Re: excalibur builds!

Leo Simons wrote:
> 
>> If you want, you can use Gump itself in the meantime.
>> Make an Avalon profile, give the classpath the jars needed that are 
>> not generated in the avalon project, and it will build any avalon 
>> project.
> 
> could you give an example? I don't want everyone to have to set up their 
> own gump workspace (ie rubix.xml). Is that possible you think?

rubix.xml is just a properties file with an XML syntax.  Drop the 
"additional projects" and "after the bootstrap", and you end up with a 
rather small file with only two things most users will need to tailor: 
basedir and user.  (To be fair, I fully expect most people will also 
want to tailor pkgdir).

If somebody wants to go down this path, I will help.  It certainly is 
easier than building each dependency with Ant.  And doesn't require any 
change to Avalon to work.

It *will* require a little trial and error to find out what the minimum 
Avalon really needs to build.  You would think that this is something 
that could be determined by analysis, but in practice it is often easier 
and more reliable to try it and see.

> - Leo

P.S.  Because of build.sysclasspath=only, I have yet to reproduce the 
excalibur build under gump, but I am confident I will.  For those 
interested in why this is so, here's two links:

http://gump.covalent.net/log/jakarta-avalon-excalibur.html
http://jakarta.apache.org/gump/why.html

I am confident that it would would if build.sysclasspath=last were 
specified, and that is something that is controllable as a property in 
the workspace.

- Sam Ruby