Community
Participate
Working Groups
Build ID: I20080617-2000 Steps To Reproduce: 1. Mirror a first Eclipse repository locally: eclipsec.exe -nosplash -verbose -application org.eclipse.equinox.p2.artifact.repository.mirrorApplication -source http://subclipse.tigris.org/update_1.4.x -destination file:c:\artifactLocalRepository\myMergedRepo 2. Mirror a second repository to the same local directory: eclipsec.exe -nosplash -verbose -application org.eclipse.equinox.p2.artifact.repository.mirrorApplication -source http://m2eclipse.sonatype.org/update/ -destination file:c:\artifactLocalRepository\myMergedRepo 3. In the local repo, everything you mirrored from the first repo will be trashed. The local directory will only be the mirror of the second one. More information: Using -append or not won't change anything. If you can reproduce, Pascal Rapicault confirmed it would likely be a bug (see http://dev.eclipse.org/mhonarc/lists/p2-dev/msg00219.html). Thanks for this great component anyway! Cheers.
Andrew has been writing tests for the mirror application and has a test which will catch this, as well as a patch for the class in question.
Created attachment 112898 [details] Added code to look for "-append" arguement modified "initializeFromArguments" to include an additional if statement to set append to true when "-append" is found. Tested using org.eclipse.equinox.p2.tests.mirror.BasicMirrorApplicationTest.java (currently not located in CVS)
Andrew, please create a CVS patch and attach it to this bug report instead of the full Java file. Let me know if you need help. Thanks.
Created attachment 112954 [details] Added code to look for "-append" argue,emt (patch version) Sorry about the confusion
This was released a while ago. Closing.
Sorry for the question, but just to be sure : the "target milestone" indicates the first released version containing the fix? So, the fix is only available since 3.5 M3? If so, any chance it gets backported to some 3.4.2 or something? Cheers
This has been released in 3.5 M3. Given that those tools are usually for a limited set of ppl (compared the the final users of p2) we have no plan to port that to 3.4.2.
Removing iplog+ from bug since it is already on the attachment.
Thanks for your answer Pascal. Thanks for the clarification. So, but I don't measure all the involvement: could we consider using p2-3.5-M3 mirrorApp to mirror & merge repositories to be used by an eclipse 3.4.x installation? Was there for example any change in the repository format that could cause problems? Cheers. Thanks a lot.
You can safely use the 3.5 (try M3) mirroring tools to produce repositories to be used with 3.4.
