Ralph Goers wrote:
Michael McCallum wrote:
why not just specify the dependencies with version ranges, if you do
there is no need to rewrite anything it just works...
My builds never use version ranges. We require that builds be
reproduceable at any time in the future. Version ranges don't
guarantee that.
Ralph, if you start using OSGi builds, you will be unpleasantly
surprised by the OSGi spec, which states that version 1.2.3 means
[1.2.3,) i.e. anything greater or equal to 1.2.3 ( See table 3.1 on page
29-278 of core spec 4.1, April 2007 )
The only way to guarantee your build reproducibility will be using
ranges like [1.2.3,1.2.3] :)
I am seriously considering the OSGi spec for Mercury, at least the
ranges part.
Oleg
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
