|
|
|
Re: Running eclipse.exe (octopus.exe) after maven tycho build does not start-up [message #1821420 is a reply to message #1819617] |
Wed, 12 February 2020 19:27 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Michael Marton![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=michi.marton%40gmail.com) Messages: 7 Registered: August 2015 |
Junior Member |
|
|
We are actually migrating our e(fx)clipse application to openJDK11 & openJFX11. Ran into several similar issues. Please see the attached files (I renamed them to eclipse_man.ini and eclipse_org.ini, resp) which work for us (openJDK11 is located under "C:\Program Files\Java\jdk-11.0.6+10", openJFX11 is located under "C:\Program Files\Java\javafx-sdk-11.0.2"). Also note that NO Windows environment variables are needed for this, at all. The eclipse launcher takes all params correctly from the "eclipse_man.ini" file if the content is correct.
BUT I have to admit that our "eclipse_man.ini" file is currently created MANUALLY due to several issues:
(1) Somehow during the build all spaces and slashes in the "--module-path" declaration are wiped (so when declaring "C:\Program Files\Java..." as VM argument in the RCP product configuration, we unfortunately get "C:ProgramFilesJava..." in the eclipse_org.ini).
(2) It seems like there is currently no way for declaring the JDK path (i.e. "-vm" parameter) via product configuration (we would like to specify the exact JDK path for each of our application releases so that e.g. different versions can be used in parallel).
Due to these issues, we currently take the "eclipse_org.ini" (original output from the Tycho build) and have to adapt it to "eclipse_man.ini" (which can then successfully start our application).
Hope this helps a bit.
[Updated on: Wed, 12 February 2020 19:33] Report message to a moderator
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04291 seconds