Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 302283 - add ability to exclude bundles when running comparator with mirror task
Summary: add ability to exclude bundles when running comparator with mirror task
Status: RESOLVED FIXED
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.6 M6   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 270627
  Show dependency tree
 
Reported: 2010-02-09 10:22 EST by Kim Moir CLA
Modified: 2010-02-10 20:28 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kim Moir CLA 2010-02-09 10:22:27 EST
In bug 270627, I'm trying to change the comparator so that it runs without skipErrors.  I can't do that today because the some of the doc bundles are updated with javadoc and thus may be different each time but the qualifier will remain the same.  I was going to update the qualifier of the doc bundles each build but Andrew suggested that it would be better if the comparator were changed so that there was an option to exclude certain bundles. The doc bundles are very large and shouldn't be downloaded each time for little benefit.
Comment 1 Andrew Niefer CLA 2010-02-10 20:28:09 EST
It looks like this:

<p2.mirror source="file:repo1" destination="file:repo2">
   <comparator comparator="org.eclipse.equinox.p2.repository.tools.jar.comparator"
               repository="file:repoBaseline" >
      <exclude>
         <artifact id="foo" version="1.0.0" />
         <artifact classifier="osgi.bundle" range="[1.0.0,5.0.0)">
             <property name="format" value="packed" />
         </artifact>
      </exclude>
   </comparator       
</p2.mirror>


on <artifact> there is "id", "classifier", "version", or "range". 
version="1.0.0" is equivalent to range="[1.0.0,1.0.0]".
<artifact> also supports nested <property> elements.

Excluded artifacts are excluded only from the comparison, they are still mirrored as before.