> -----Original Message-----
> From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> Catastrophic dependency failure insurance:
>
> Suggestion from Geir Magnusson Jr: if at the completion of every
> successful build, the output jars are copied to a well
> defined location
> and then this location is used as the source for resolving
> dependencies,
> then we have a system that automatically upgrades. I
> kinda like this
> idea, and am curious what other people think...
>
> This discussion was motivated by yesterday's xml-xerces
> build failure...
For what it's worth, I'm using this option for my global build here and it
seems to work fine so far, but like you I'm in an exploratory approach.
[...]
> Future plans:
>
> Once I get the DTDs for Gump closer to Alexandria's, I
> still plan on
> spliting this profile out to a separate CVS module with a
> considerably
> larger base of committers. I do plan to get back to the Python
> implementation, I'm also planning on adding in the
> various exolab J2EE
> projects - hence the motivation for enhancing the way that
> repositories
> are defined.
I'd like to take the opportunity to ask you a question about build
definition.
currently, the option taken is to take advantage of the
build.sysclasspath=only option to have a perfect control about what is
needed or not by the project.
This is fine. However this is not correct if the build takes advantage of
external libraries that are needed to perform the build. If you are forced
to put lib A v1.1 for a Ant taks while you are using lib A v1.0 to compile
your source, then you need to put both lib A v1.0 and 1.1 in the classpath
use for compiling the source code. Thus you cannot guarantee that it will
compile with only lib. v1.0. :-(
I have not yet found a solution to this problem, so question is. any idea ?
:)
--
Stéphane Bailliez
Software Engineer, Paris - France
iMediation - http://www.imediation.com
Disclaimer: All the opinions expressed above are mine and not those from my
company.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
