Steve,you can reap benefits of automatic maven-like JAR management in ANT by usng Greebo optional ant task:
I took a look at Maven about six months ago. The promise is great but it is not as sophisticated as ANT. In general, it is only appropriate for tasks as simple as grab source, get associated jars, compile, build new jar. This fits in nicely with the Commons project but not really for our use. We have just too many legitimate targets.
(http://greebo.sourceforge.net/faq.html) as long as you have access to repositories that have all required JAR files such as
ibiblio maven repository: http://www.ibiblio.org/maven/
there was apparently effort to do this in Apache but it seems dead now (?!): http://www.apache.org/dist/java-repository/
alek
-----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 3:14 PM To: [EMAIL PROTECTED] Subject: Re: What do I need to build/test?
Sanjiva Weerawarana wrote:
"Tom Jordahl" <[EMAIL PROTECTED]> writes:
We have avoided checking in some jar files to our tree to prevent version
lock or skew. If you drop (most of?) these jars in xml-axis/lib, they
will get picked up automatically by the ant scripts. I wouldn't be
opposed to checking in copies of stuff to the tree, but its unclear
if we can distribute Sun stuff (activation, mail, etc) per the license.
+1 for creating a "buildlib" directory into which all these jars are committed. Not for distribution at all, but for simplified building.
Also, +1 for committing the optional stuff too.
I'm all for making it easy to get the stuff in, but once you put it in CVS you have to worry about (a) the gump and (b) keeping it all up to date.
ultimately java needs the CJAN equivalent of CPAN; Both Maven and Khrysalis projects are trying to do better auto-fetch of components needed for a build. Maybe we should look at them...
-- If everything seems under control, you're just not going fast enough. —Mario Andretti
