Thanks for all of the input; it was very helpful (reading hype on a
project website is one thing; hearing day-to-day experiences with the
build tools is quite another. :) Thanks!
Robert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
On Dec 26, 2006, at 11:15 AM, Art Gramlich wrote:
Where's Hatcher to plug ant? :-)
These days I mostly am dealing with Rake, but thus far at a Ruby
newbie user level. I will be getting fancier with Rake very shortly
though.
Where do I stand with Maven? Never even really used it other t
If you want to stick with Ant but are more familiar with Java you
could use Gant (Groovy Ant scripting).
http://groovy.codehaus.org/Gant
-warner
On Dec 23, 2006, at 9:54 PM, Robert Zeigler wrote:
Without starting a flame-war... ;)
I'm about to embark on updating a very brittle build process
Where's Hatcher to plug ant? :-)
For us, ant has worked well and pretty much stayed out of the way
(like a build tool should).
Additionally, because of the widespread use, almost every tool has an
ant task (e.g. sablecc).
It looks like there are several scripting tasks now available for the
I just ran across an innocative, upcoming tool for Ant that might
make your life a great deal easier. It's called Virtual Ant:
http://www.placidsystems.com/virtualant/Default.aspx
regards,
-tom
At 09:54 PM 12/23/2006, you wrote:
Without starting a flame-war... ;)
I'm about to e
I'll tell you that I'm still a fan of well organized ant scripts.
Yes, ant can get messy. (like Make!) Yes, ant has no dependency management.
(If you really care to move in that direction, look at Ivy.) Yes, Ant is XML
based, and XML is ugly.
BUT
It's the best java tool out there for complex pr
>As an example of the kinds of problems that "high-level automation"
>can bringOur project needed to use some specific libraries that
>came with the XXX software package. I figured out the Maven incantation
>to correctly 'install' these libraries to our local repository using one
>of the Maven
At 02:57 AM 12/24/2006, you wrote:
ANT:
If you want to be like most every over Java project in the world, use
Ant. It works fine. Just be sure to always remember: PROPERTIES ARE
IMMUTABLE.
MAVEN:
If you want to get a lot of extra bells and and whistles, such as
having all your dependencies aut
ANT:
If you want to be like most every over Java project in the world, use
Ant. It works fine. Just be sure to always remember: PROPERTIES ARE
IMMUTABLE.
MAVEN:
If you want to get a lot of extra bells and and whistles, such as
having all your dependencies automatically downloaded, versioned, an
.
Maven is also flexible -to an extent- in adapting to your existing project
structure.
- Original Message
From: Warner Onstine <[EMAIL PROTECTED]>
To: jug-discussion@tucson-jug.org
Sent: Saturday, December 23, 2006 10:26:53 PM
Subject: Re: [jug-discussion] build tools...
My pe
I second maven. It is an excellent build tool, just make sure you use maven 2
cause its much cleaner than maven 1. Actually I just finished
upgrading some existing projects at work from maven 1 to use maven 2.
Bashar
My personal preference is Maven, it makes the build process very
easy. One
My personal preference is Maven, it makes the build process very
easy. One of the caveats with Maven is that you will *probably* have
to sacrifice your build structure in order to gain that ease. But on
the plus side it simplifies things a great deal. If this is a
direction you're intereste
Without starting a flame-war... ;)
I'm about to embark on updating a very brittle build process. It's
currently based on a combination of relying on the IDE + a bit of ant
In all honesty, I know make better than I know any other build tool, but
I'd rather not do this build in make. So, I'm looking
13 matches
Mail list logo
