on 8/13/01 10:55 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote:
> The key common target is "dist", because that's the one that creates the
> JAR files, in a "dist" directory underneath each package directory. All
> the other targets follow one of a couple styles, depending on who
> contributed the original code (I gave up on fighting for a standard --
> it's a losing proposition).
No it isn't. Take my approach on things:
Do it. Let people complain with patches.
> Knowing about "dist" leaves only the dependency order to worry about.
> For that, you've got two choices:
Neither of which I particularly like.
> * Use released versions off the web site when possible (beanutils
> and digester right now, but you need current CVS code for the
> workflow stuff to build).
>
> * Change directory to the jakarta-commons top level directory and
> run "ant dist". It calls the subordinate build scripts for many
> of the packages (at least the ones I use :-) in the correct order
> to deal with dependencies.
YUCK!
> We *badly* need CJAN/JJAR/whatever-the-heck-it's-going-to-be-called. I'd
> like to see it done, but don't have time to help.
I have been working in Turbine land to create a unified build system over
the last week. We are getting closer, particularly in the area of
implementation of ${lib.repo} and dependency definitions. It makes setting
things up a breeze and also prepares us for CJAN based definitions because
the dependencies are clearly defined as well as targets to find them.
-jon
