Jump to content
Excelsior Forums


Excelsior Staff
  • Content count

  • Joined

  • Last visited

Everything posted by dbg

  1. That's right. Use JET Control Panel for creating .prj and JetPackII for .jpn project files. You can create them once and use to build the application from command line any number of times.
  2. Hello Jorge, In order to build your application from command line you can use JET project files prepared with GUI tools. To compile executable launch the following command jc =p Compilation-project.prj To create package run xpack Packaging-project.jpn For more information see "Excelsior JET User’s Guide", chapter "Tomcat Web applications", section "Overview", subsection "Automated builds"
  3. dbg

    Application with multiple versions of JRE

    Hello Radu, Excelsior JET does not allow to package executables compiled with different Java versions together. Also note that current version of Excelsior JET supports Java 6 only, Java 5 is not supported.
  4. dbg

    Remove class names from native EXE

    Excelsior JET is a certified Java SE implementation. Due to license restrictions, certified implementation should contain all Java SE APIs including reflection API. Compiler cannot prove that your application never uses reflection API, as in Java a new class can be dynamically loaded at any time and it can use reflection API. So the class and method names should be preserved in the compiled application. Note that parameter names are not included in reflection information and not preserved. To avoid appearing of class and method names in the executables, Excelsior JET has an option to encrypt such strings. It can be enabled in JET Control Panel on the page TARGET in "EXECUTABLE SETTINGS" panel. For more information see JET User's Guide, chapter "Intellectual property protection", section "Data protection"
  5. dbg

    Can code compiled by JET be stolen?

    Excelsior JET provides code protection through ahead-of-time compilation: it takes your jars and classes as input, compiles them to optimized native code, and produces a conventional executable. After compilation, bytecode is no longer needed and it is not included into the resulting executable. The native code is much harder to reverse engineer compared to Java bytecode. To make sure that all your class files are compiled, open your project in JET Control Panel on the page CLASSPATH and check that "Protect" column contains "all classes" for application jar files. You can read more about code protection here