This turned out to be a bug in the site.jsl. A patch has been applied
to svn and this will be fixed in version 1.10 of the xdoc plugin.
Here is an example site generated using the patched plugin and
maven.xdoc.theme=classic
maven.ui.banner.background=#fff
On 9/12/05, Phil Steitz [EMAIL PROTECTED] wrote:
On 9/12/05, Niall Pemberton
[EMAIL PROTECTED] wrote:
From: Phil Steitz [EMAIL PROTECTED]
They do, but including the commons about us menu before the component's
menu is in the commons-site.jsl
commons-site.jsl has the following line:
On 9/11/05, Niall Pemberton [EMAIL PROTECTED] wrote:
- Original Message -
From: Brett Porter [EMAIL PROTECTED]
Sent: Monday, September 12, 2005 2:36 AM
I think this option I raised earlier got missed, so I'll repeat here:
The one option I'd consider is whether it is worth
From: Phil Steitz [EMAIL PROTECTED]
On 9/11/05, Niall Pemberton [EMAIL PROTECTED] wrote:
- Original Message -
From: Brett Porter [EMAIL PROTECTED]
Sent: Monday, September 12, 2005 2:36 AM
I think this option I raised earlier got missed, so I'll repeat here:
The one option I'd
On 9/12/05, Niall Pemberton [EMAIL PROTECTED] wrote:
From: Phil Steitz [EMAIL PROTECTED]
They do, but including the commons about us menu before the component's
menu is in the commons-site.jsl
commons-site.jsl has the following line:
jsl:applyTemplates select=$nav/body/[EMAIL
There does not appear to be a reasonable way to make our customized
site.jslwork with both pre- and post-
1.9 versions of the maven xdoc plugin. The best solution is to upgrade to
1.9+ before generating commons sites. I also just fixed a problem in
commons-site.jsl that we preventing the date
Hi Phil.
Phil Steitz wrote:
There does not appear to be a reasonable way to make our customized
site.jslwork with both pre- and post-
1.9 versions of the maven xdoc plugin. The best solution is to upgrade to
1.9+ before generating commons sites. I also just fixed a problem in
commons-site.jsl
On 9/11/05, Brett Porter [EMAIL PROTECTED] wrote:
Hi Phil.
Phil Steitz wrote:
There does not appear to be a reasonable way to make our customized
site.jslwork with both pre- and post-
1.9 versions of the maven xdoc plugin. The best solution is to upgrade to
1.9+ before generating
Phil Steitz wrote:
Given the current setup above, unless I am missing something, all of the
maven.xml's would have to be modified to check, I guess this is possible.
Fair enough - I thought all the projects extended
commons-build/project.xml (and hence used it's maven.xml).
Is there any way
From: Brett Porter [EMAIL PROTECTED]
Phil Steitz wrote:
Given the current setup above, unless I am missing something, all of the
maven.xml's would have to be modified to check, I guess this is possible.
Fair enough - I thought all the projects extended
commons-build/project.xml (and
On 9/11/05, Niall Pemberton [EMAIL PROTECTED] wrote:
From: Brett Porter [EMAIL PROTECTED]
Phil Steitz wrote:
Given the current setup above, unless I am missing something, all of
the
maven.xml's would have to be modified to check, I guess this is
possible.
Fair enough - I
- Original Message -
From: Phil Steitz [EMAIL PROTECTED]
On 9/11/05, Niall Pemberton [EMAIL PROTECTED] 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
On 9/11/05, Phil Steitz [EMAIL PROTECTED] wrote:
On 9/11/05, Niall Pemberton [EMAIL PROTECTED] wrote:
From: Brett Porter [EMAIL PROTECTED]
Phil Steitz wrote:
Given the current setup above, unless I am missing something, all of
the
maven.xml's would have to be modified to
We have Subversion now, and so svn:externals, which gives us an alternative
to having to check out commons-build separately...
This still has 2 problems:
- you end up with X checkouts of commons-build where X is the number of
projects in commons you have checked out
- You also have to do a
- Original Message -
From: Brett Porter [EMAIL PROTECTED]
Sent: Monday, September 12, 2005 2:36 AM
I think this option I raised earlier got missed, so I'll repeat here:
The one option I'd consider is whether it is worth ditching
commons-site.jsl altogether. I have no idea what it
I opened a new bug for this incompatibility issue.
http://jira.codehaus.org/browse/MPXDOC-167
Arnaud
-Message d'origine-
De : Niall Pemberton [mailto:[EMAIL PROTECTED]
Envoyé : lundi 12 septembre 2005 06:14
À : Jakarta Commons Developers List
Objet : Re: [commons-build] Site
Sorry guys, I made the jsl change, which was to make site builds work with
versions 1.9+ of the xdoc plugin. I thought I had tested successfully with
1.8, but now see that I must have failed to clear the plugin cache or
something. My bad. So...current state is that commons-site.jsl *requires*
It seems this maven problem affects all the commons projects that use the
commons-build. I'm seeing it on Linux and Windows, both running Maven 1.0.2.
Again, the problem is when running maven site. When it gets to the jdepend
report, I see:
xdoc:jelly-transform:
[echo] Generating
, 2005 5:52 PM
To: Jakarta Commons Developers List
Subject: [commons-build] Site build problem
It seems this maven problem affects all the commons projects that use the
commons-build. I'm seeing it on Linux and Windows, both running Maven 1.0.2.
Again, the problem is when running maven site. When
Developers List
Subject: [commons-build] Site build problem
It seems this maven problem affects all the commons projects that use the
commons-build. I'm seeing it on Linux and Windows, both running Maven
1.0.2.
Again, the problem is when running maven site. When it gets to the
jdepend
report
List
Subject: Re: [commons-build] Site build problem
Didn't help. Besides, I thought Maven would download plugins automatically
from the network. By upgrading, I downloaded the 1.5 jar and put it in my
maven home /plugins directory. Any other ideas?
Don
On 9/9/05, James Carman [EMAIL PROTECTED
: Re: [commons-build] Site build problem
Didn't help. Besides, I thought Maven would download plugins automatically
from the network. By upgrading, I downloaded the 1.5 jar and put it in
my
maven home /plugins directory. Any other ideas?
Don
On 9/9/05, James Carman [EMAIL PROTECTED
The problem is the update that was made to commons-site.jsl 9 days ago:
http://tinyurl.com/dvab5
If you reverse out that change the problem goes away.
Niall
- Original Message -
From: Don Brown [EMAIL PROTECTED]
Sent: Friday, September 09, 2005 10:52 PM
It seems this maven problem
23 matches
Mail list logo