Re: maven roadmap - should i stay or should i go

[Joakim Erdfelt]

Brett Porter wrote:
Huh... Exactly how much trouble are we talking about to switch custom
plugins and such??? Is Jelly replaced? 
   

Yes, though we are trying hard to put in a replacement that can
transparently run old Jelly scripts with minimal changes. Part of the
problem is that people have come to rely on bugs in Jelly/Jexl/Maven
for their scripts to work.
 

Will there be a facility in the new (maven 2) POM to specify the default
goals required to build the artifact (either fully stated ${pom.goals} 
or determined by some other variable ${pom.type}?). Also will there be
a means to specify plugins and their minimum version requirements 
in the dependencies?  I think I caught talk about even specifying the 
difference in dependencies between build/run/test/cactus/integration time,
is this categorization the ability I'm looking for?

/* Joakim Erdfelt */
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]