"Maven to me (still) looks like a great tool for single module
applications/libraries - but not so much for big(ger) multi module apps. "
--> When reporting is concerned.
Jan Vissers wrote:
The really bad documentation is already mentioned, and rightly so!
Also, I feel for multi module projects (every meaningful JEE project)
the reporting part is really awful.
There is no consistency in the reporting plugins.
Maven to me (still) looks like a great tool for single module
applications/libraries - but not so much for big(ger) multi module apps.
Eric Redmond wrote:
Hi all Maven users!
I'm beginning a study to outline the real reasons that people have for
avoiding Maven. My questions to you all are:
What were your anxieties about using Maven? If you use Maven: what
helped
you make the decision? If you don't: why did you avoid it?
Here are some that I have heard in the past:
* Lack of good documentation.
* Community unwilling to help me with my problems.
* Not "industry supported" or "mainstream" enough.
* I don't like conforming to the Maven project layout.
* My project is too complex to switch.
* There are not enough plugins available.
* We already have a large investement in tool X.
* I have to build native/non-Java code.
Any more reasons? Care to expand these ideas?
Thanks for your help!
____
Eric Redmond
http://codehaus.org/~eredmond
---------------------------------------------------------------------
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]
