I've run modeler under Java 5 Update 4 and Java 6. Aero works under Java 6. I've had no time yet to test Java 5 Update 15 or something.
Demetrios, the issue seems to be caused my java settings in your system. Do the following: 1. Check JAVA_HOME env variable 2. If it's empty, check registry value at HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\CurrentVersion One of those must be pointing to Java 5. You need to change it to Java 6. 2008/11/17, Andrey Razumovsky <[EMAIL PROTECTED]>: > > Strange.. "java -jar" also uses JAVA_HOME, so JDK must be the same. I'll > test tonight when I'll have Vista access > > 2008/11/17, Andrus Adamchik <[EMAIL PROTECTED]>: >> >> Ah ok, I guess I lost track of the original problem. >> >> So exe-file must be built using Java 6 (the Java NSIS script points to). >>> Jar >>> should be built with 1.5, still. >>> >> >> I am not a big expert on NSIS, but from looking at the script (that I >> grabbed off of the NSIS Wiki examples), it uses JAVA_HOME or "current JVM": >> >> ReadRegStr $R1 HKLM "SOFTWARE\JavaSoft\Java Runtime Environment" >> "CurrentVersion" >> ReadRegStr $R0 HKLM "SOFTWARE\JavaSoft\Java Runtime Environment\$R1" >> "JavaHome" >> StrCpy $R0 "$R0\bin\javaw.exe" >> >> EXE itself is a thin wrapper that starts CayenneModeler.jar, so I guess >> the problem is multiple VM's installed on the same machine, with the script >> picking the wrong one?? >> >> Andrus >> >> >> On Nov 17, 2008, at 9:58 AM, Andrey Razumovsky wrote: >> >> It works, but I see the same effect Demetrios does. I can confirm it's >>> annoying. >>> The problem is, that Java5 (at least before Update 9) doesn't support >>> Vista's new UI theme, called 'Aero'. So, when java app with Swing starts, >>> screen blinks and a message pops up, telling Aero has been disabled. >>> So exe-file must be built using Java 6 (the Java NSIS script points to). >>> Jar >>> should be built with 1.5, still. >>> >>> I've read that Aero is supported in 1.5.0 update 9, not only 1.6. So I >>> could >>> test modeler built with that JDK. Let me create a JIRA issue >>> >>> [1] >>> >>> http://www.microsoft-watch.com/content/operating_systems/windows_vista_aero_glass_and_java_dont_mix.html >>> >>> 2008/11/17, Andrus Adamchik <[EMAIL PROTECTED]>: >>> >>>> >>>> Before we fork the distro, I'd like to understand what exactly doesn't >>>> work, and is there a confirmed fix. Like I wouldn't expect a problem >>>> running >>>> bytecode compiled with Java 5 on the Java 6 JRE for instance. >>>> >>>> BTW, here is the NSIS descriptor that is used to assemble the .exe: >>>> >>>> >>>> >>>> https://svn.objectstyle.org/repos/woproject/trunk/woproject/woproject-ant-tasks/src/resources/japplication/windows/app.nsi >>>> >>>> But from what you are saying the problem is with the bytecode, not the >>>> exe? >>>> >>>> Andrus >>>> >>>> >>>> On Nov 17, 2008, at 9:12 AM, Andrey Razumovsky wrote: >>>> >>>> Maybe create another POM for Vista? >>>> >>>>> >>>>> 2008/11/17, Andrey Razumovsky <[EMAIL PROTECTED]>: >>>>> >>>>> >>>>>> I have Vista and I've seen this problem even if I start modeler from >>>>>> Eclipse. I think this is JDK version problem - installed java in your >>>>>> system >>>>>> is 1.6, which supports Aero, that's why 'java -jar'. >>>>>> >>>>>> I don't know how Windows' exe is built in Cayenne, but I suppose we >>>>>> should >>>>>> somehow build it with Java 6 not Java 5. >>>>>> >>>>>> 2008/11/16, Robert Zeigler <[EMAIL PROTECTED]>: >>>>>> >>>>>> >>>>>>> I've started to get into the habit of always specifying the version >>>>>>> for >>>>>>> not only deps, but plugins in maven. >>>>>>> It's the only way to have a long-term stable build with maven. >>>>>>> >>>>>>> Robert >>>>>>> >>>>>>> On Nov 16, 2008, at 11/1611:06 AM , Aristedes Maniatis wrote: >>>>>>> >>>>>>> >>>>>>> On 17/11/2008, at 3:04 AM, Andrus Adamchik wrote: >>>>>>> >>>>>>>> >>>>>>>> We test things on Vista and see what we can do to make the exe work >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> I notice that maven-japplication-plugin has been updated a few >>>>>>>> times in >>>>>>>> the last few months and our maven target doesn't specify a release >>>>>>>> version >>>>>>>> number. Has the problem started just recently? Should we add a >>>>>>>> version >>>>>>>> number to the pom? >>>>>>>> >>>>>>>> Ari >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> --------------------------> >>>>>>>> ish >>>>>>>> http://www.ish.com.au >>>>>>>> Level 1, 30 Wilson Street Newtown 2042 Australia >>>>>>>> phone +61 2 9550 5001 fax +61 2 9550 4001 >>>>>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>> >> >
