Afaik, starting a 32-bit Eclipse (arch=x86) on 64-bit VM or vice versa does not work. At least, it doesn't work for me on Win Server 2008 R2 64-bit with Eclipse Classic 4.3.0 and Oracle JRE 7u25.
Anyway, I've just got a similar problem when Eclipse 3.6 (win 32-bit) would not start org.eclipse.equinox.p2.director application at all with IBM J9 VM (1.6.0-build2.4). The exact same Eclipse would start without any issues if I don't specify -application argument. It turned out that the problem was caused by these lines in eclipse.ini: > -vm > jdk/jre/bin/javaw.exe After I replacing them with the following ones, p2 director started working again. > -vm > jdk/jre/bin So, maybe javaw.exe was the culprit in your case too. /Mikhail ----- Ursprungligt meddelande ----- Från: "frank jakop" <[email protected]> Till: "P2 developer discussions" <[email protected]> Skickat: onsdag, 21 aug 2013 8:54:10 Ämne: [p2-dev] Antwort: Re: Antwort: Re: Standalone plugin update via p2 I tried wit a fresh Juno download and it worked. That's ok but strange nevertheless, because all that was changed was the -vm parameter in the eclipse.ini (pointed to a 64-bit VM). Installing by UI (Help->Install new software...) always worked. Thanks for helping! Frank [email protected] schrieb am 21.08.2013 08:44:29: > Von: > > Pascal Rapicault <[email protected]> > > An: > > P2 developer discussions <[email protected]> > > Datum: > > 21.08.2013 08:45 > > Betreff: > > Re: [p2-dev] Antwort: Re: Standalone plugin update via p2 > > Gesendet von: > > [email protected] > > I'm running the following command on a plain eclipse download and get results > > ./eclipse -nosplash -application org.eclipse.equinox.p2.director - > listInstalledRoots > > I'm wondering if your installation is busted. If you try to install > something using hte p2 UI, does it work? > > > On 08/21/2013 08:36 AM, [email protected] wrote: > Thanks for the director hint. When I try to list/install/uninstall > IUs, for example like this > > eclipsec.exe -nosplash -application org.eclipse.equinox.p2.director > -listInstalledRoots > > I get every time > > !SESSION 2013-08-21 08:33:07.929 > ----------------------------------------------- > eclipse.buildId=4.3.0.I20130605-2000 > java.version=1.7.0 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE > Framework arguments: -product org.eclipse.epp.package.jee.product > org.eclipse.platform -application org.eclipse.equinox.p2.director - > listInstalledRoots > Command-line arguments: -os win32 -ws win32 -arch x86 -product > org.eclipse.epp.package.jee.product org.eclipse.platform - > application org.eclipse.equinox.p2.director -listInstalledRoots > > !ENTRY org.eclipse.equinox.p2.core 4 0 2013-08-21 08:33:08.678 > !MESSAGE Unknown option org.eclipse.platform. Use -help for a list > of known options. > > Am I missing something? > > Regards > > Frank > > > [email protected] schrieb am 21.08.2013 08:05:26: > > > Von: > > > > Mikhail Kalkov <[email protected]> > > > > An: > > > > P2 developer discussions <[email protected]> > > > > Datum: > > > > 21.08.2013 08:06 > > > > Betreff: > > > > Re: [p2-dev] Standalone plugin update via p2 > > > > Gesendet von: > > > > [email protected] > > > > Hi, > > > > I think the following two commands should be sufficient. To start > > with, obtain the list of all features explicitly installed into > > Eclipse (aka roots): > > > /path/to/eclipse -nosplash -application > > org.eclipse.equinox.p2.director -listInstalledRoots > > Then, perform an update operation for the desired roots against > > desired p2 repos: > > > /path/to/eclipse -nosplash -application > > org.eclipse.equinox.p2.director -repository http:// > > download.eclipse.org/releases/kepler -uninstallIU root1,root2,etc - > > installIU root1,root2,root3 > > > Kind regards, > > Mikhail Kalkov > > > > > Från: "frank jakop" <[email protected]> > > Till: [email protected] > > Skickat: onsdag, 21 aug 2013 7:10:27 > > Ämne: [p2-dev] Standalone plugin update via p2 > > > > Good morning, > > > > up to Indigo there was a nice possibility to update my eclipse > > installation's plugins headless via org.eclipse.update.standalone > application. > > > > This has been replaced with the p2 API since Juno, relating to > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=311590 > > > > Is there any documentation how to achieve a headless update for an > > eclipse installation with the p2 API? > > > > Best Regards > > > > Frank > > _______________________________________________ > > p2-dev mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/p2-dev > > _______________________________________________ > > p2-dev mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/p2-dev > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
