You are right Stuart, the example is wrong. In the automatic case, the
micro part is dropped.
Kind regards,
Peter Kriens
On 9 sep 2008, at 02:57, Stuart McCulloch wrote:
2008/9/9 Sahoo <[EMAIL PROTECTED]>
bnd documentation [1] says that it uses micro part of version.
Shown below
is relevant portion of the documentation:
/During processing, bnd will attempt to find the exported version of
imported packages. If no version or version range is specified on
the import
instruction, the exported version will then be used though the
*micro* part
and the qualifier are dropped. That is, when the exporter is
|1.2.3.build123|, then the import version will be 1.2.3. If a
specific
version (range) is specified, this will override any found version.
However,
[EMAIL PROTECTED] can be used to substitute the found version in a range. /
actually that does say the micro part *will* be dropped unless you
specify
an
explicit version on the import - but the example shown keeps the
micro part.
I think the example on the BND website is wrong, and it should be
"1.2", but
hopefully Peter can clarify what is the expected result - looking at
the
code
the micro part is definitely dropped on purpose...
Thanks,
Sahoo
[1] http://www.aqute.biz/Code/Bnd
Richard S. Hall wrote:
I think I remember Peter saying something about this. I think it
is a
"feature", trying to add some flexibility. I could be wrong.
-> richard
Sahoo wrote:
Stuart McCulloch wrote:
2008/9/8 Sahoo <[EMAIL PROTECTED]>
the simple workaround would be to manually fix the version to
the micro
level - but note
that version="0.3" is short for version="[0.3,?)" which does
include the
"0.3.18" version
so you might find that the trimmed version still works for you
do you see any exceptions / problems when you use the bundle
with the
trimmed version?
Although trimmed version works for me, I am afraid that it will
match
with versions that I don't want it to. Ideally, a good version
management
policy (like micro version only for bug fixes) should have
avoided such
worries, but we don't have such a good policy enforced.
Since this package is imported in a lot of files, it is rather
cumbersome
to fix all the poms to specify the version. Hence, I was looking
for a fix
to the plugin. Having said that, I understand if this can't be
fixed
immediately.
Thanks,
Sahoo
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Cheers, Stuart
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
