on 8/21/01 1:11 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote:
> The philosophy used in all the non-Turbine implementations of build
> scripts :-) is that you *don't* define everything in the local project's
> build.properties -- you only code the exceptions. Therefore, you would
> define lib.repo in your project's file if you *didn't* want to use the
> standard one in your home directory.
And I'm asserting that that philosophy is broken. It is much clearer to
allow a project to define its dependencies so that when you download the
project, you clearly know what it needs (by only looking at its
build.properties) in order to build it.
Right now, I look at any one of the commons projects and it gives me a
headache trying to figure out what each one needs in order to build things.
That clearly shows that the philosophy is broken.
Even lamer is the fact that the build.xml files reference base directories
AND jar files instead of just the single jar files. Who was smoking crack
when they implemented that?????????
Eventually, this information will be moved into a JJAR system, but it is
still up to the project to define this information.
> See my previous message for a real-life scenario where your proposed way
> creates an inability to do what *I* as a developer need to do.
See my response. As a developer, I can't even compile any of the commons
projects without spending 20 minutes on each build.properties file because
they are such a fucking inconsistent mess.
Telling me that I should use the top level build.xml file to compile *every
single project at once* is just plain nuts. I only want to compile the
projects that I care about and I want them to install their .jar files in
one location with correct version numbering so that I can easily reference
them with lib.repo.
Sorry to sound so pissy, but I want to spend time with your *wonderful*
workflow code and not on fixing the 50 damn build system dependencies so
that I can even compile it in the first place.
Craig, you know code and I'm always impressed with your abilities to define
amazing stuff, but I'm sorry, your build systems have never been truly easy
to use. I want to help with that, please let me.
-jon
