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]
