I'm sorry to hear that you are moving to Maven.
When I see Maven files in a project, I often just give up there.
It is a complex and fragile build system that obscures light,
robust tools.
After installing Maven, developers then enable every Maven
feature. The current build of Groovy from from Subversion takes
31 minutes, before it fails. The Groovy developers now start to
coach me through repeated 31 minute builds. It's a non-starter.
The JRuby build is pure ant and takes a few minutes.
You have SVN, Ant, and Javac.
Once a project goes to Maven, there is an enormous barrier to
entry for those developers, like myself, who are not going to
put up with it. I don't need a PMD report every time I change a
line of code.
I hereby volunteer to check in the dependencies into Subversion,
or write Ant scripts that will put the dependencies via http
from the source of your choosing.
It should take a day to write. If you must go with Maven, please
accept my offer as an alternative.
I simply do not understand why people put up with Maven, why
everyone thinks it is such a great idea. It's turning Java land
into binary-only land.
This is not a rant. I'm sincerely concerned that Maven will be
a productivity drag and retard participation.
* Developer must have Maven installed, cannot simply type "ant".
* Maven has an enormous set of dependencies itself.
http://www.custommonkey.org/words/jeff/2005/02/23/1109162220000.html
* BSF acutally has a small set of depenencies.
* At least explore alternatives.
http://blog.exis.com/colin/archives/2005/03/10/ivy-is-everything-maven-should-havecould-have-been-25-years-ago/
Again, I'm willing to set something up.
Cheers.
--
Alan Gutierrez - [EMAIL PROTECTED]
- http://engrm.com/blogometer/index.html
- http://engrm.com/blogometer/rss.2.0.xml
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
