Hi,

Is there a timeline (or at least some idea of a timeline) when the current 
release issues will be resolved and when blueprint 0.4.1 will be released?

In general I think that the module-release issue which was addressed in various 
mails before this (e.g. Jean-Baptiste Onofré's mail from March 16th) cannot be 
resolved unless semantic versioning is introduced. Version range imports are 
already done by the maven bundle plugin, so building a bundle with some version 
of the bundle (e.g. util 0.3) will result in package imports like 
org.apache.aries.util.tracker;version="[0.3,1)" already now; so as long as the 
semantic versioning is really maintained (which means that the version 0.5 is 
compatible to 0.3) having one bundle installed that was built with util 0.3 and 
one that was built with util 0.5 is supposed to work (when util 0.5 is 
installed).

Of course there is some issue with testing this stuff... This could be resolved 
by having version ranges in the bundle version of the maven dependencies (e.g. 
[0.3,1)) and re-running the tests of all released versions, but that means that 
a bundle is always built with the newest available version of a bundle (and the 
maven bundle plugin will also take the package versions from that bundle, even 
if this is not necessary).

Best regards
Stephan

Reply via email to