Community
Participate
Working Groups
Build Identifier: I20110613-1736 If I run a successful build and then run validate again the content.jar is deleted. I would not expect anything in the build/final directory to be touched by a validation pass. If I then try to regenerate content.jar by running build again I get the following error: java.lang.ClassCastException: org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository cannot be cast to org.eclipse.equinox.p2.repository.artifact.IFileArtifactRepository at org.eclipse.b3.aggregator.engine.Builder.getAggregationArtifactRepository(Builder.java:730) at org.eclipse.b3.aggregator.engine.Builder.initializeArtifactMirroring(Builder.java:1004) at org.eclipse.b3.aggregator.engine.Builder.run(Builder.java:1650) at org.eclipse.b3.aggregator.presentation.AggregatorActionBarContributor$BuildAggregationAction$1.run(AggregatorActionBarContributor.java:292) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) If I run the build again it does not fail, but the metadata can sometimes be broken. Reproducible: Always Steps to Reproduce: 1. Run a repo build and wait for it to complete successfully 2. Validate the model 3. Check if content.jar is present (should not be) 4. Run a build again - get CCE.
*** Bug 362963 has been marked as a duplicate of this bug. ***
IMO Validation should not mess with the final build output. Currently deletes stuff, e.g. content.jar. Thomas H. agrees this is wrong.
*** Bug 352995 has been marked as a duplicate of this bug. ***
Fixed in http://git.eclipse.org/c/b3/b3.git/commit/?id=7102cb98dc7d0f3e83d5e90f189b0b9061e59a23
I can confirm that validation does not now alter the final build output directory in any way. Thanks. Closing.
[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI. Made no changes to assignee's for closed bugs, even though some were old inbox.]