James Carpenter wrote:
If I wait a few months will all my problems simply disappear with maven
magicially supporting what I need?
As Oleg pointed out: no. Even if Mercury landed today and it were
bug-free, you can bet that a significant portion of the Maven plugin
ecosystem wouldn't work properly with non-standard local repository layout
(e.g. if the filenames didn't have version numbers).
Once a non-standard repository layout were written, you could probably add
some integration tests for the core plugins that you depend on and
eventually get those tests to pass, but it'd be a big (Sisyphean)
struggle, because most people wouldn't use a custom local repository.
Instead, we should make sure your needs are satisfied whenever we get
around to changing the default local repository layout. There's at least
one outstanding proposal to do this today:
http://docs.codehaus.org/display/MAVEN/Local+repository+separation
You'll recall that I put together a long proposal document about this in
the past; I've extracted a small part of it, relevant to your problem, and
made it available here:
http://docs.codehaus.org/display/MAVEN/Modify+Local+Repository+Layout+to+Support+finalName
I don't know when we intend to try to change the default local repository
layout (probably in 3.0, which was previously called 2.1) but somewhere in
that timeframe we should seriously consider changing the local repository
layout to at least incorporate Brett's proposal and perhaps also my
proposal.
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
