Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 262234

Summary: [publisher] Support .qualifier on SiteXMLAction
Product: [Eclipse Project] Equinox Reporter: Andrew Niefer <aniefer>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: henrik.lindberg, thomas
Version: unspecified   
Target Milestone: 3.5 M6   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on:    
Bug Blocks: 241441    

Description Andrew Niefer CLA 2009-01-23 15:30:57 EST 
If a site.xml has .qualifier in it for features included in categories, then we should construct a range when quering for matching feature IUs.  

See pde.build's Utils.createVersionRange(String) for creating ranges where 'qualifier' is involved.  I don't know how the OmniVersion thing affects ranges here.

This affects building update sites in the UI.
Comment 1 Thomas Hallgren CLA 2009-01-23 18:15:24 EST 
The Omni Version is fully compatible with the OSGi Version and if used the same way as in Utils.createVersionRange(String), the outcome should be the same. You should be fine just copying that code and replace the OSGi Version/VersionRange with its Omni counterparts.

Are you experiencing any problems with this approach or was it just a general question?
Comment 2 Andrew Niefer CLA 2009-01-26 10:39:58 EST 
This was a general question, particularly in the case of a version like "1.0.0.ab_qualifier".  In build, the range is created by incrementing the "ab_" to "aba" ( Z < _ < a ) to yield the range [1.0.0.ab_, 1.0.0.aba)
Comment 3 Andrew Niefer CLA 2009-02-11 13:46:39 EST 
Done without needing to calculate ranges in the same way build does.