Community
Participate
Working Groups
Build Identifier: I20100429-1549 I'm creating a product for Win/Linux and the Mac, no problems with our build environment on 3.5.2. Since I've started using 3.6M7 our build fails while installing the features for the mac bundle. Generation of win/linux product works as expected. !ENTRY org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2010-05-04 13:34:20.022 !MESSAGE Error while loading manipulator. !STACK 0 java.lang.IllegalStateException: The framework persistent data location (/Users/o/Sources/workspace.go/build/_build.N/go/N-N20100504-1215/PROVEtechGO-N20100504-1215-macosx-cocoa-x86_64/GO.app/Contents/MacOS/configuration) is not the same as the framework configuration location (/Users/o/Sources/workspace.go/build/_build.N/go/N-N20100504-1215/PROVEtechGO-N20100504-1215-macosx-cocoa-x86_64/configuration). at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.checkConsistencyOfFwConfigLocAndFwPersistentDataLoc(EquinoxManipulatorImpl.java:65) Reproducible: Always Steps to Reproduce: 1. Product build with installation of additional bundles from external repo
No idea or workaround while this gets fixed?
Andrew does that ring a bell? I would have said that this is related to the capitalization issue we had in the metadata. Make sure that the name of you application is capitalized (e.g. Foo.app).
I need more details to reproduce. I have 2 example product builds which add extra features using additional director calls. Both work fine for me. If you want to run them, be sure to modify the (builder/)build.properties to add a macosx config. http://aniefer.blogspot.com/2009/07/composing-and-updating-custom-eclipse.html http://aniefer.blogspot.com/2009/07/adt-part-2-more-like-epp.html
configs = win32,win32,x86 & macosx,cocoa,x86_64 & linux,gtk,x86 The application is already capitalized (GO.app) after filing bug 277460. I have two director calls via Ant (PDE headless build), the first installs the product feature and the second additional features. The error occurs calling the director for the second time on the mac product and it uses the same arguments as for the win install.
I've found a workaround, just call the director once ;- But why does it fail on the second one?
If I want to make an update from within the finished product via UI, I get the same error, Mac only.
We're seeing the same issue on our finished RCP product. When installing additional feature through Help->Install New Software..., the following exception occurs: !ENTRY org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2010-07-22 13:57:03.057 !MESSAGE Error while loading manipulator. !STACK 0 java.lang.IllegalStateException: The framework persistent data location (/Applications/Aptana Studio 3/AptanaStudio3.app/Contents/MacOS/configuration) is not the same as the framework configuration location (/Applications/Aptana Studio 3/configuration). at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.checkConsistencyOfFwConfigLocAndFwPersistentDataLoc(EquinoxManipulatorImpl.java:65) at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.loadWithoutFwPersistentData(EquinoxManipulatorImpl.java:348) at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.load(EquinoxManipulatorImpl.java:319) at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:54) at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:107) at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.installBundle(InstallBundleAction.java:80) at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.execute(InstallBundleAction.java:32) at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:35) at org.eclipse.equinox.internal.p2.engine.Phase.mainPerform(Phase.java:149) at org.eclipse.equinox.internal.p2.engine.Phase.perform(Phase.java:78) at org.eclipse.equinox.internal.p2.engine.PhaseSet.perform(PhaseSet.java:44) at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:73) at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44) at org.eclipse.equinox.p2.operations.ProvisioningSession.performProvisioningPlan(ProvisioningSession.java:174) at org.eclipse.equinox.p2.operations.ProfileModificationJob.runModal(ProfileModificationJob.java:79) at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.equinox.p2.engine 4 4 2010-07-22 13:57:03.081 !MESSAGE An error occurred while installing the items !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2010-07-22 13:57:03.081 !MESSAGE session context was:(profile=AptanaProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]ch.qos.logback.classic 0.9.19.v20100519-1505, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2010-07-22 13:57:03.081 !MESSAGE Error while loading manipulator. !STACK 0 java.lang.IllegalStateException: Error while loading manipulator. at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:58) at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:107) at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.installBundle(InstallBundleAction.java:80) at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.execute(InstallBundleAction.java:32) at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:35) at org.eclipse.equinox.internal.p2.engine.Phase.mainPerform(Phase.java:149) at org.eclipse.equinox.internal.p2.engine.Phase.perform(Phase.java:78) at org.eclipse.equinox.internal.p2.engine.PhaseSet.perform(PhaseSet.java:44) at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:73) at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44) at org.eclipse.equinox.p2.operations.ProvisioningSession.performProvisioningPlan(ProvisioningSession.java:174) at org.eclipse.equinox.p2.operations.ProfileModificationJob.runModal(ProfileModificationJob.java:79) at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Found a workaround by adding -startup ../../../plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar to the <product>.ini file.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
The mac layout has completed changed since this bug report, so I'm doubtful that this issue remains in the current releases.
