Community
Participate
Working Groups
Today the jvm parameters from the product configuration are copied by the export wizard into the <lancher>.ini . Under MacOSX however there is an addditional config file which seem to override that information - the info.plist . Please make sure that either the jvm parameters from <lancher.ini> are not overriden by info.plist or let the wizard add the parameter to the info.plist, too.
*** Bug 115231 has been marked as a duplicate of this bug. ***
confirm that the current behavior is correct.
I can confirm that the parameters setup in the ini are taken into account. Everything works as expected.
I just upgraded to 3.2.0 and the problem still persists. Setting the instance area in the product configuration via vm parameters has no effect: -Dosgi.instance.area=@user.home/Lago/LagoPict Any suggestions ? (Sorry for the late reply)
In the integration build from Thu, 22 Mar 2007 the problem still persists. The exported info.plist does not contain any vm-args. Is any work planned on this ?
I would blame this on bug 164762
Is this still a problem for you with a recent build? (e.g. since bug 164762 was fixed)
Created attachment 64292 [details] screenshot of .product I can confirm that the <myproductname>.ini is now placed correctly. But there seems to be a bad sideffect: the vm arguments from the product configuration are not exported to the ini anymore. eclipse-SDK-I20070418-1012-win32
marking as works for me. We have never inserted arguments into the info.plist file. There is an explicit warning not to add vm arguments to the info.plist because they do over-ride the launcher .ini