>
>
>
> 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
>
> http://people.apache.or
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.js
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:
>
>
>
> but site.jsl (from 1.9.2) has
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:
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 wheth
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:
- 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 wha
>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
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
- 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, a
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.
> > >
>
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/projec
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
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 ge
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.
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 bei
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* v.
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 prob
tjdo-plugin-1.0.0
> maven-uberjar-plugin-1.2
> maven-vdoclet-plugin-1.2
> maven-war-plugin-1.6.1
> maven-webserver-plugin-2.0
> maven-wizard-plugin-1.1
> maven-xdoc-plugin-1.8
>
> -Original Message-
> From: Don Brown [mailto:[EMAIL PROTECTED]
> Sent: Friday
opers 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,
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]> wrote:
>
> I had to upgrade one of the maven pl
I had to upgrade one of the maven plugins to fix that, I believe. Which
version of the jdepend plugin do you have? I'm at version 1.5. I'm not
absolutely sure that's the plugin that I upgraded.
-Original Message-
From: Don Brown [mailto:[EMAIL PROTECTED]
Sent: Friday, September 09, 200
22 matches
Mail list logo