commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton" <niall.pember...@blueyonder.co.uk>
Subject Re: [commons-build] Site build problem
Date Mon, 12 Sep 2005 00:15:01 GMT
----- Original Message ----- 
From: "Phil Steitz" <phil.steitz@gmail.com>


> On 9/11/05, Niall Pemberton <niall.pemberton@blueyonder.co.uk> wrote:
>> I did a quick scan and only "attributes" and "chain" extend the
>> commons-build/project.xml - but maybe all commons components should?

> That used to be the setup, and lots of people complained, since it meant
> that even to just build/jar the components, you had to have commons-build
> checked out, among other things. Of course, the web sites now depend on
the
> commons-site.jsl, style sheets and nav elements, so you effectively have
to
> have it checked out to do site gens, so it is worth considering going back
> to extending.

OK, my suggestion:

1) Add a dependency for the 1.9.2 maven-xdoc-plugin to the commons-build's
project.xml
2) Add a commons-site-xdoc-1.8.jsl to commons-build that reflects
commons-site.jsl before you made your change - i.e. doesn't require the
1.9.2 maven-xdoc-plugin.
3) Post an [all] message to this list that explains the issue and telling
projects they have a choice of three solutions a) extends
commons-build/project.xml or b) add a plugin dependency to their project.xml
or c) change their project.properties to point to commons-site-xdoc-1.8.jsl.
Then its down to individual projects which way they want to jump.

Niall

P.S. Put notes in the two jsl files explaining the difference between the
two.



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message