On Tue, 2007-08-28 at 06:00 +0200, Jan Kriesten wrote: > to make a long story short: maven is fine if the project is setup and > maintained > for it. else it gets a real pain. >
Isn't that the result of a poorly maintained project that uses *any* build process, whether it be Maven, Ivy, Ant, Make, or even their own custom script? The tool really should not be blamed for difficulty compiling poorly maintained projects. Maven is there to make it easier for the dev team to keep the project in order, but it sure doesn't make up for any lack of due diligence. Thankfully, the wicket team does their due diligence, and as a result, it is *much* easier for me to compile, check dependencies, build javadoc, or whatever else I need to do. -- Philip A. Chapman Desktop and Web Application Development: Java, .NET, PostgreSQL, MySQL, MSSQL Linux, Windows 2000, Windows XP
signature.asc
Description: This is a digitally signed message part
