By jsugrue
via java.dzone.com
Published: Nov 03 2009 / 04:59
... in other words, a first step towards using Maven for dependency management but NOT builds. That's the irony of Maven ... they've conflated two things (dependency management and builds) in such as way that they make the useful one (dependency management) painful because the build system is so awful.
-
10 New Tools and Resources for Developers and Designers
-
Google Phone Coming - How Will This Affect Market Dynamics - iPhone Hacks
-
KiGG Design And Architecture – Part 2 Project Structure
-
Popular Websites Free Clone Scripts
-
Using arrays from arrays.xml in Android
-
Does 10x faster development dumb down programming?
Comments
michele.mauro replied ago:
The Sonatype Maven team have replied:
http://www.dzone.com/links/maven_howard_how_to_execute_the_perfect_oss_drive.html
It has to be noted, however, that Howard Lewis Ship and his Tapestry framework have always been a world apart from "mainstream" java frameworks and directions...
serps replied ago:
I understand his pain, but I'm not sold on his solution.
xcdesz replied ago:
Eh.. he is right about the flakiness of the m2Eclipse plugin. If you have a system with many modules (i.e; >10), then it seriously effects the performance and stability of your Eclipse. Also, you shouldnt need a plugin/IDE for a build system. If your build system cannot run from a command line, then it is too complicated.
wytten replied ago:
Yes, and it gets worse if your central repository is geographically distant :(
Voters For This Link (12)
Voters Against This Link (17)