I hate to turn this into a Maven discussion, but there seems to be
some confusion here. One of Maven's appeals (like Rails) is
convention over configuration. By default, Maven looks for java in
src/main/java and tests in src/test/java. These directory locations
are all configurable <http://maven.apache.org/guides/introduction/
introduction-to-the-pom.html#Super%20POM>. Maven certainly has its
weak points (e.g. phase attachments in plug-ins), but in my
experience, centralized artifact repositories and not having to re-
invent the build process for every project certainly outweighs these.
Justin
On Nov 13, 2007, at 3:30 PM, Michael Terrington wrote:
Jean-Yves Cronier wrote:
For information, we have already encountered many problems with
Eclipse + Ivy (via IvyDE). This is one reason why we use Maven now
for our projects.
In addition, thanks to Maven, we used lots of things that improve
the quality of our developments and documentations (especially
thanks to "Maven site" generation).
The main drawback of Maven is in the projects structure. Java
Sources have to be in [src/main/java] and resource files in [src/
main/resources], the level of testing in [src/test/java], etc.
I hope this little feedback can be helpful
Interesting. Just to prove YMMV, we switched from Maven to Ant +
Ivy for much the same reasons...
