On 29/03/2007, at 1:03 PM, Brian E. Fox wrote:

Brett,
I can see some logic to this as it's just another shade of grey between
the current snapshot repo and central. It does however feel a little
like a hack to work around some version ranging issues. I think
massembly is a good example of where this is needed, but perhaps mdep is
a case where it's not. This is still in "alpha" because there are more
goals planned to be added. While the plugin overall is alpha, some of
the original goals (copy/unpack, etc) are quite mature and very stable. If we did this, it would raise the bar a little higher for people to get
useful functionality.

Good point, but shouldn't that stable functionality be in the previous release, which folks should still be using in production until they need to upgrade?

<snip stuff I agree with>


The only thing that is slightly annoying is when you have plugins with
goals that are both meant to be bound and some for the CLI. When you put a plugin in to pluginManagement, this applies even to the CLI versions. I'm not sure if/how we could make this better but here's the use case: I
use mdep to unpack and copy stuff so I set 2.0-alpha-3 (example). But
now I want to prepare for 2.0.6 and want to run dependency:analyze and I want 2.0-alpha-4, I have to change my pluginManagement. I guess a way to
override PMgt from the CLI would be sufficient here.


You can actually do this (yet another not well documented thing):

mvn org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:analyze

It's pretty grotesque - and I think better ways to manage pure CLI plugins vs lifecycle ones in terms of versioning are definitely needed. We had a stab with plugin-registry, but it wasn't all that successful. It's actually a whole category of use cases to revise - like how to easily select your repositories from the CLI when you don't have a POM, etc. Thanks for bringing it up!

Cheers,
Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to