Modularization of Alexandria build

[Jeff Martin <je...@synamic.co.uk>]

At the moment the alexandria.xml file allows people to build either the
whole set of documents or some subsection (menu, content, jxr)

I would like to allow a greater degree of control of what is built so that
different parts could be build with different frequencies. I would be nice
to be able to just rebuild a single module or just a single section of docs
within a module.

So far I've not really settled on a good way to do this (mostly due to not
having spent enough time examining what actually happend during the build). 

I've been thinking of three ways to acheive this and just thought I'd run
them past people before I actually dive in.

1) Try to create a more unique set to ant targets eg modulename_javadoc,
modulename_build.
2) Seperate each module into it's own build file.
3) Use ant properties and the if attributes to allow a properties file to be
used to configure which parts are run.

Anyone got any thoughts on the subject?

Re: Modularization of Alexandria build

["Kevin A. Burton" <bu...@relativity.yi.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeff Martin <je...@synamic.co.uk> writes:

> At the moment the alexandria.xml file allows people to build either the
> whole set of documents or some subsection (menu, content, jxr)
> 
> I would like to allow a greater degree of control of what is built so that
> different parts could be build with different frequencies. I would be nice
> to be able to just rebuild a single module or just a single section of docs
> within a module.

Yes... I agree

> So far I've not really settled on a good way to do this (mostly due to not
> having spent enough time examining what actually happend during the build). 

Just an XSLT parse on the first phase... build.xml on the second.  You could
just setup a system to change your XPath select on the XSLT and you should be done.

> I've been thinking of three ways to acheive this and just thought I'd run
> them past people before I actually dive in.
> 
> 1) Try to create a more unique set to ant targets eg modulename_javadoc,
> modulename_build.
> 2) Seperate each module into it's own build file.
> 3) Use ant properties and the if attributes to allow a properties file to be
> used to configure which parts are run.
> 
> Anyone got any thoughts on the subject?
<snip>

Maybe have the XPath queries in a properties file... then you can adjust this at
runtime.

Kevin

- -- 
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
             Cell: 408-910-6145 URL: http://relativity.yi.org

Any programming language is at its best before it is implemented and used.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt

iD8DBQE6C3Q2AwM6xb2dfE0RAtDQAJ94hVW9oCNTI0s4bNipC1+oCfiOwgCgtE9L
k1IT736e224AAEO6EZ5nGcI=
=Po+u
-----END PGP SIGNATURE-----



NSA PLO spy SEAL Team 6 bomb class struggle Panama Semtex Honduras KGB DES $400
million in gold bullion Waco, Texas kibo fissionable