John Morrison wrote:
>
> > It should be easily downloadable though. Perhaps after we write up the
> > standard on Jakarta's web site we can add a link to the skeleton build.xml
> > file.
>
> I think things still need adding to the skeleton. Also - what about
> multi-component builds? The skeleton is really orientated to single
> component projects...
There is no standard for that.
We have such a beast with Avalon Cornerstone. The approach we took when trying
out the standard on for size was to have the main build targets perform the
same target on each of the component builds. It feels a bit cumbersome, so I
am open to suggestions.
There is the possibility to replicate some of the functionality to a specific
component with the following format:
ant componentname-all componentname-check
Where "componentname" is the name of the component you want. This too feels
kludgy. Especially since your build.xml file will become overly large and
cumbersome to maintain.
The Cornerstone project has a separate build.xml file for each component. The
component build file has all the responsibilities of the main build file (but
it must be able to act in a self contained manner).
The above approach has some issues as well as there is duplication of build
process in each component's build file. Sometimes I think that build files
that behaved like Java class inheritance would be perfect. Implementing it
would not be fun though.
The bottom line is I can't think of an elegant solution to this problem.
If a project goes this route, then we must assume that the project is more
familiar with Ant--so we can prescribe a more complex approach. For the
average project, there is only one component.
> > You are right. I just looked at Avalon's setup, and it only has
> > two entries:
> >
> > <property file=".ant.properties"/>
> > <property file="${user.home}/.ant.properties"/>
> >
> > That allows a .ant.properties file in the ${base.dir} to override
> > properties in build.xml as well.
>
> Isn't that the same as <property file="build.properties"/> ?
Yep. Just needs a standard name for the file--personally, I like
"build.properties" better.
> I'll do the mods and repost the build.xml file tomorrow.
Sounds good.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
