Ant Now A Top Level Apache Project
hardcorejon writes "Am I the only person who didn't notice that on November
18th 2002, the Apache Ant Project had migrated out from under the Jakarta Project umbrella to become a top-level Apache project, joining the ranks of the Apache HTTP Server Project?
Well, for those of us who use Ant on a regular basis, this is great news. Ant is an incredibly powerful tool, increasingly a standard build system for many new projects."
info about ant
-- I was raised on the command line, bitch
Will it be patched to work in space?
Am I the only person who didn't notice that on November 18th 2002, the Apache Ant Project had migrated out from under the Jakarta Project umbrella to become a top-level Apache project, joining the ranks of the Apache HTTP Server Project?
Ummm... yes? As you said yourself, it's been there since nov. 18th. Anyone who's been to their website has noticed (whether they actively noticed it or not).
Good thing this isn't on the front page. And is a very useful tool but it's not worth mentioning "oh, btw, ant got moved to the main apache screen back in last november". If you noticed it then, then it *might* be worth a small announcement (not sure even that is warranted). Noticing it now, who cares?
This is somewhat off-topic, but reading about Ant remembered me of a question I've been meaning to ask the net for some time now. Since it involves software for building software, this thread may be a good place to do it (and it's only karma, anyway :-)
For a long time I've been wishing that there was an alternative to autoconf. I mean, autoconf is useful, and I still don't know of a better way to build complex stuff on a lot of platforms. But it is painfully slow on small machines, it's hell to make it run on Win32, and it is way too complex, requiring you to write scripts that run through three different interpreters (sh, m4 and make), each with more than their fair share of syntactic weirdness and idiosyncrasies.
(I'm using it for a product we're developing in my company, and I'm the only one who knows how the build system works. It's black magic for everyone else. I do work with very competent programmers, but only I have the patience for making autoconf scripts. Granted, we push it a bit hard: one of our targets is Win32. That part is the worse. Cross-compiling and running from cygwin, with libtool and all that, is tough shit. Every now and then I get so pissed off with it that I start writing plain Makefiles, one for each architecture/OS. Then I reconsider, realize the maintenance hell that would become, and go back to work even blacker magic on the acinclude.m4's... *sigh*)
So, this Ant here I welcomed with high hopes some months ago, and then dumped it just as fast. The thing is: it's Java. It requires you to install a JVM to build a project. Some of our build machines, the most exotic ones, are so small that I would say they're barely able to run the monstruous configure scripts that autoconf creates... So, run a JVM. Right.
Also, when I tried it, Ant was good to build Java stuff, but required some serious hacking to make it build C or C++ (or anything else, for that matter). Since it was targeted to build projects on essentially one platform (Java), it's really hard to make it check for availability of libraries or headers, and to define macros for conditional compilation and stuff. And of course, it didn't have all that "knowledge" autoconf has accumulated over the years, with regard to the subtle peculiarities of each platform. So I found Ant to be nothing more than a fancy make. And I already have make.
So, I'd like to ask: Is Ant any better for non-Java stuff these days? Is someone using it for non-Java projects? And, while I'm at it, does anyone know of a practical alternative for autoconf?
Well, It's good to see we're getting help from other parts of the animal kingdom. I'll be careful not to step on it.
Repeal the DMCA!
Ant (apparently) was always a top-level project, it just kinda got a little userped by jakarta. Actually the whole jakarta/apache comunity has had quite a change recently.. Many projects have been promoted to top-level, there's new "management" and things appear a lot more organised.
Imho, I think this was over-due as it was getting a little confusing. I hear talk at one point that apache would become another source-forge, but I'm glad to see the (oldest, most well-known, most respected?) OSS project has maintained focus.
- For open source Java projects I want to distribute the source code in the binary.
- It is nice to be able to view the source code of the application from the application by using the classloader.
- When everybody has the source, anybody can modify it.
Ant also does not have a spell check module, something that is really easy to put into make.There's a better one out there - jam.
It's used mostly by the OpenBeOS project.
Is Ant worth a look by an organization that is moving a large commercial C++ app from windows only towards platform portability? I'm the first to say that MS's NMAKE sucks, and a lot of the new blood in the organization wants to move to something significantly better. Are there tools/addins/modules for Visual C++ command line compilers? to automatically maintain header & library dependencies for C++?
-Mike
http://www.a-a-p.org/
looks promising
Several Jakarta Subprojects are becoming top level projects:
db.apache.org (OJB and Torque)
avalon.apache.org (The Avalon server framework).
Plus Tapestry is moving into Jakarta. If you look around there really is a lot going on over at Apache, especially within the Jakarta projects.
Who said Freedom was Fair?
tool that illustrates the worst abuse of using XML.
The idea of having XML representing a build syntax is ridiculous - it's verbose and hard to read.
Ant is designed by morons for morons.