No, using a spec of 1.0 should give you 1.0.
It was an implementation decision to give best compatibility with the
use-nearest conflict resolution and the existing POMs (if all such
versions were treated as "must be 1.0", then most transitive deps
would fail because most dependencies declare different versions).
Given the chance to do over, I'd change it.
- Brett
On 07/11/2006, at 6:36 PM, Hilco Wijbenga wrote:
On 11/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
That's the defined behaviour.
Ok, so using a spec of '1.0' is wrong? Should VersionRange not
complain then? I don't understand why '1.0' and '[1.0]' are not the
same.
---------------------------------------------------------------------
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]
