• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About snowman

  • Rank
  • Birthday January 1

Contact Methods

  • Website URL

Profile Information

  • Gender
  1. Better late than never:
  2. We now have an official Maven plugin:
  3. For Reflection and JNI to work, only the names of classes, methods, and fields are needed, not the bytecode. It is perfectly possible in many cases to compile the entire Java app to native code and ship it without the original class files. That said, there are libraries and APIs that are designed to work with bytecode or rely on the presence of bytecode at runtime. One notable example of the latter are the security providers. Refer to the following Excelsior JET Knowledge Base article for details: HOWTO: Compile an application that uses a security provider The log files emitted by the Excelsior JET compiler contains full information about which classes it compiled.
  4. Please elaborate on the steps to reproduce this. If you compile and package your app with default settings, rt.jar is not used at all and should not be packaged for distribution. When you enable the Global Optimizer, rt.jar will only contain those standard Java library classes that were not precompiled, so most, if not all, of those classes are not actually used by your app.
  5. Excelsior JET 11 beta 1 is available for three platforms: Windows/x86, OS X, and Linux/x64. Windows/x64 and Linux/x86 support is in the works. Notable changes compared to version 10.5: Java SE 8 and JavaFX 8 support Details and downloads
  6. Excelsior JET actually had such technology since the second public beta and up to and until version 3.7. It was called JetPerfect, and it enabled you to cram an SWT app onto a 1.44MB floppy disk. But there were two big problems with it: It was extremely fragile - any use of reflection or JNI at run-time could break things completely. One client compiled their SWT app on a system where the mouse had no wheel, and it blew up on its client's systems when SWT tried to load the respective class dynamically. It was illegal - the Java SE license did not permit subsetting the API. (It still does not, with the exception of Compact Profiles introduced in Java 8, but, of course, today you can just take OpenJDK and throw away whatever you want.) That's why we dropped JetPerfect from version 4.0, which was the first certified Java Compatible. But even if there were no legal issues, the wheel-less mouse incident alone would have been enough to trigger the decision.
  7. A number of old tests get a new life every time we add support for another target architecture or platform. Here comes a fresh record from our labs: Main Thread Lives Two Lives
  8. Sorry, these forums are not monitored daily. The best way to ensure a fast response is to reach out to the Excelsior JET engineering team directly by email at I also apologize if we left an impression that it is necessary to purchase a license to receive any support. We do provide support during the evaluation period, but we had public holidays on Nov 3-4, and are now working through a backlog, so please bear with us. Finally, rest assured you will receive a full refund if we fail to resolve the issue you've encountered.
  9. I would not call this "near future", but better late than never:
  10. Here are the most notable changes in Excelsior JET 10: OS X Support The 64‑bit versions of Excelsior JET, Professional and Enterprise Editions are now available for Apple OS X desktop operating system. 64-bit Version Improvements OS X support Application performance improvements evidenced by industry‑standard and popular benchmarks: SPECjvm2008 and SPECjbb2002 composite scores improved by more than 25% 20% to 60% speedups observed on the DaCapo benchmark suite etc. [*]Executable sizes reduced by 15-25% Download Your 90-Days Evaluation Copy
  11. Thank you very much for sharing your opinion, shashaank. You may wish to subscribe to our mailing list or RSS feed to make sure you will receive any updates on this subject matter that we may issue.
  12. First of all, make sure to copy the EXE file that was processed by the packager (JetPackII), not the EXE originally emitted by the compiler. If you build a new EXE, you have to re-package it before copying to other PCs; there is a command-line tool for that called xpack. Also, if you do not have the latest update installed (for Excelsior JET 9 it is Maintenance Pack 2 as of today), install it then rebuild and re-package your app. If nothing helps: What are your friend's operating system and its language settings?
  13. When you say "much smaller market", are you comparing by the potential number of users or by potential revenues and profits? If the latter, do you have solid market data to support your opinion?
  14. Not the license per se, but the open legal dispute between Google and Oracle over Java. Desktop and mobile are converging. Is Surface Pro 3 a desktop or mobile device? And UI redesign is required in the case of RoboVM as well. An Android app won't look native on iOS. We will surely do that when/if time comes. Thank you very much for sharing your opinion and advice.
  15. Members of Excelsior senior management not only read this forum, but also post replies. Excelsior is an Oracle Java licensee, hence our solution would have to be Java SE compliant, whereas the RoboVM author had chosen to use the Android standard library, so as to aid portability between iOS and Android.