Re: Fortress binary (success)

[Leo Simons]

How to take ant to the limit with avalon-excalibur
--------------------------------------------------
Set ${lib.dir} in ~/.ant.properties (and in ~/ant.properties to be safe) to your central library location. It's in common use in many ant-based projects.

There's a few more, like avalon-site.dir and jakarta-site.dir which you can just set to ${lib.dir}/.. or something similar, as all that's normally needed in that case is the contents of that module its lib/ dir. This is on the TODO for changing to make more sense though :D

Then, you want to scan some of excalibur's default.properties files for properties ending in '.lib:

grep -o -P '^(.*).lib=' fortress/default.properties;

Change all those to ${lib.dir} as well.

To live on the edge, set ${build.lib} to point to ${lib.dir} as well, and when you build a project, the jar ends up into your big repo dir.

I used to have a pretty big ~/.ant.properties. I pretty much ditched it in favour of a local gump install though.

sample .ant.properties
----------------------
lib.dir = ~/repo/jars
build.lib = ${lib.dir}
avalon-site.dir = ${lib.dir}/..
jakarta-site.dir = ${lib.dir}/..

avalon-framework.lib=${lib.dir}
logkit.lib=${lib.dir}

excalibur-container.lib=${lib.dir}
excalibur-instrument.lib=${lib.dir}
excalibur-instrument-manager.lib=${lib.dir}
excalibur-i18n.lib=${lib.dir}
excalibur-event.lib=${lib.dir}
excalibur-sourceresolve.lib=${lib.dir}
excalibur-xmlutil.lib=${lib.dir}
excalibur-logger.lib=${lib.dir}
excalibur-datasource.lib=${lib.dir}
excalibur-pool.lib=${lib.dir}
excalibur-component.lib=${lib.dir}
excalibur-cache.lib=${lib.dir}
excalibur-testcase.lib=${lib.dir}
excalibur-monitor.lib=${lib.dir}
# list goes on for other projects.... :D


cheers,

- Leo



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]