| Summary: | Profile modified twice during one update operation | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Natalia Bartol <natalia.bartol> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.7.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
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 automated Eclipse Genie. |
Build Identifier: M20110909-1335 When performing an update of a feature in Eclipse 3.7.1 based product two .profile files are created. The only difference between them is the removal of STRICT inclusion rule for the feature that is being updated: Initial profile: <iuProperties id='com.x.a.feature.feature.group' version='1.0.0.201110081930'> <properties size='2'> <property name='org.eclipse.equinox.p2.internal.inclusion.rules' value='STRICT'/> <property name='org.eclipse.equinox.p2.type.root' value='true'/> </properties> </iuProperties> First profile created by update operation: <iuProperties id='com.x.a.feature.feature.group' version='1.0.0.201110081930'> <properties size='1'> <property name='org.eclipse.equinox.p2.type.root' value='true'/> </properties> </iuProperties> Final profile after update: <iuProperties id='com.x.a.feature.feature.group' version='1.0.0.201110082048'> <properties size='2'> <property name='org.eclipse.equinox.p2.type.root' value='true'/> <property name='org.eclipse.equinox.p2.internal.inclusion.rules' value='STRICT'/> </properties> </iuProperties> Could anyone give me a hint why is this “middle” profile created? I could not reproduce this issue in pure Eclipse 3.7.1 itself: during update just one new .profile is created. This case is problematic not only because more disk space is used for storing .profile files. When Automatic Updates with downloading option is enabled an error occurs: !ENTRY org.eclipse.core.jobs 4 2 2011-10-10 13:13:37.975 !MESSAGE An internal error occurred during: "Automatic updates download". !STACK 0 java.lang.IllegalStateException: Profile myProfile is not current. Expected timestamp 1318248562066 but was 1318248511220. at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry.lockProfile(SimpleProfileRegistry.java:758) at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:67) at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44) at org.eclipse.equinox.p2.operations.ProvisioningSession.performProvisioningPlan(ProvisioningSession.java:151) 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) It seems to be caused when Automatic Updates Download job reads profile that is being modified by Update Operation. Any help will be appreciated. Reproducible: Always