Another option is using Savant. Savant provides a nice wrapper around
Ant that allows you to create plugins which can be used between
projects. The plugins are simply Ant build scripts which are
downloaded prior to executing Ant. It also allows you to create
targets specific to your project or define all your targets inside
your project without using any plugins.
Lastly, Savant manages dependencies well and doesn't do any magic
upgrading or version mangling. All dependencies are explicit and it
also has a notion of local integration builds that allow you to work
across multiple projects easily.
You can also setup local Savant repository to ensure all your
dependencies are secure and Savant also allows you to secure the
repository using SSL and HTTP basic authentication.
For all the Inversoft projects I use two separate repositories with
Savant:
http://savant.inversoft.org - for all 3rd party and open source
dependencies as well as the standard Savant plugins (uses HTTP only
with no authentication)
https://savant.inversoft.com - for Inversoft dependencies (uses SSL
and HTTP basic authentication)
-bp
On Aug 18, 2009, at 11:43 AM, Boring, Jeff W (N-Viper) wrote:
Maven is not an option but thanks guys for the opinions! Any ideas
about
the unable to delete?
Jeff
Lockheed Martin
-----Original Message-----
From: Dominique Devienne [mailto:ddevie...@gmail.com]
Sent: Tuesday, August 18, 2009 12:29 PM
To: Ant Users List
Subject: Re: Unable to delete file
On Tue, Aug 18, 2009 at 10:21 AM, Martin Gainty<mgai...@hotmail.com>
wrote:
here in the US DOD vendors are converting their build.xml and
implementing to maven for:
offline repository(secure from middle-eastern attackers)
version-specific SCM tagging
security (ability to enforce SSH handshake to ftp via sftp and scp)
http://www.sonatype.com/people/2009/04/how-to-convert-from-ant-to-maven-
in-5-minutes/
I'm sure Maven has come a long way since I looked at it,
and it does encapsulate a lot of good practices, but it's
my-way-or-the-highway
philosophy went against the grain for me.
Using Ant doesn't "force" you to have a badly designed monolithic
build, although I grant you it doesn't prevent it like Maven does. In
the past, if something's wrong with your Maven build, good luck
troubleshooting it, whereas Ant is easier IMHO, although again this is
an old experience (and the Maven user list didn't help me solve it
either. Hopefully their community has evolved since).
Code with non clear dependencies is bad in any build system. Your blog
post IMHO confuses cleaning the code and switching build system. The
declarative nature of poms is good, but it can be leveraged using
Ivy+Ant rather than Maven.
All this to say that going from Ant to Maven is a lot more complex
that you make it sound, and that Ant is not really the issue here, but
the design of the code and its build. --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional commands, e-mail: user-h...@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional commands, e-mail: user-h...@ant.apache.org
