On 25 Apr 07, at 8:09 AM 25 Apr 07, Jörg Schaible wrote:
Hi devs,
how will Maven handle the problem of a dependency that should be
used in two different versions? This applies to all project that
release a new (normally major) version that can be used with the
old version at the same time. This is currently possible at least
with:
jmock 1.x / jmock 2.x
webworks 1.x / webworks 2.x
Maven supprts currently only two "versions" of sa dep if
"groupId:artifactId" is different between those two versions/
branches, but this might not be always the case. In Gentoo Linux
such a situation is solved by introducing a "slot" indicating two
different development trees that can be installed at the same time.
For Maven this would mean that the separation between (main)
artifacts should switch to "groupId:artifactId:slot", where slot is
0 by default
Is there already a proposal or doc for such kind of functionality
in a future release that I might have been missed?
Sorry, I'm not sure I fully understand what you're talking about. If
you want a specific version of something why would we use a slot,
when you can specify the version? If you want to use Webwork 1.x then
you specify the version. Many versions sit happily together in the
repository. Or are you talking about behavior that should be
constricted to a certain version range? For example, in selecting the
latest version of the 1.x family?
I'm honestly not sure what you're talking about. Maybe a problem
trying to translate Gentoo speak to Maven?
Jason.
- Jörg
---------------------------------------------------------------------
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]
