Carlos Sanchez-4 wrote:
>
> When you build A you don't know anything about C-2.0.1 because it does
> not exist.
> Versions in repository explicitly define what versions the have been
> released against or tested with.
> If I release A 2.0 depending in C 2.0
> and then I want to say i'm compatible with C 2.0.1 I have to update
> myself releasing A 2.0.1, because people using A 2.0 may not be
> compatible with C 2.0.1 and don't want automatic change of version
>
The CLR versioning meta-data is for runtime, not compile time like maven.
Also it's designed for closed source software, not open source. So perhaps
the idea is not a good fit for maven's compile time dependency management.
Sorry to trouble you.
Carlos Sanchez-4 wrote:
>
> because people using A 2.0 may not be compatible with C 2.0.1 and don't
> want automatic change of version
>
Yes, you nly get what you ask for, and version mapping should only used if
you know that it's a good mapping, or if you are testing that same mapping.
Only then can you know it's a good substitution.
David
--
View this message in context:
http://www.nabble.com/Repository-Policy-tf2306302.html#a6415851
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
