On 5/6/05, Jamie Bisotti <[EMAIL PROTECTED]> wrote: > One command this...one command that...geesh! > > http://jira.codehaus.org/browse/MPWAR-30 >
I'll respond to your comment here, instead. You said: " I've mentioned this before on the mailing list...Maven needs to be careful to balance "the Maven way" vs. making things that should be trivial, hard on users. As someone mentioned above, this is strictly about packaging within a WAR; separate projects just to get your classes JAR'ed and placed in WEB-INF/lib is extreme overkill." The reason why I was only tending towards a negative vote and not flat out -1 is because of the reason you cite here. We don't go out of our way to make things difficult for users. Bear in mind something trivial, as you say, can easily be implemented in the user's maven.xml themselves. The reasons why I am leaning towards the negative on this: I've not received one good reason why this is actually useful. "It would be nice" with no justification just means we would be adding something of little value. Feature creep is a big problem in Maven 1.x, and it has lead to some of the plugins being quite confusing because you can do one thing in a large number of ways. It makes maintenance, testing and documentation harder. I know this feature seems trivial, but you have to draw the line somewhere. As long as we aren't stopping people from doing what they need to, I think this is the right choice to make. I also don't agree with your overkill statement. More than it should be perhaps, and Maven's mutliple project handling could be better, but at the end of the day you are moving 1 or 2 directories and creating two small files for the new subproject. That's not a lot for proper separation of code and presentation. Hope this clears it up, and am happy to field any more questions or concerns on the topic. Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
