Re: Using maven 2 on non-MSFT platform to build JEXL

2009-12-08 Thread henrib
So I did something really stupid on my end possibly not having commons parent installed; I don't understand how I corrupt it repeatedly but good news is my latest try seemed successfull. My apologies to all for shouting wolf. Siegfried Goeschl wrote: > > Shall I upload the site? > > Cheers, >

Re: Using maven 2 on non-MSFT platform to build JEXL

2009-12-08 Thread Niall Pemberton
On Tue, Dec 8, 2009 at 9:22 PM, henrib wrote: > > > > Niall Pemberton wrote: >> >> >> I don't really under stand the "commons-parent pom is just above >> jexl's trunk" comment as in our subversion hierarchy its not *above* >> and the only way it can find it is by downloading/installing in you

Re: Using maven 2 on non-MSFT platform to build JEXL

2009-12-08 Thread Siegfried Goeschl
Shall I upload the site? Cheers, Siegfried Goeschl henrib wrote: > If it is styled in Blue - as the Jexl 1.0 site looks - and if you have the > menu for reports (cobertura, etc), then you're good and I'm doing something > totally stupid on my end. > If site is styled in Red, no menu for reports

Re: Using maven 2 on non-MSFT platform to build JEXL

2009-12-08 Thread henrib
Niall Pemberton wrote: > > > I don't really under stand the "commons-parent pom is just above > jexl's trunk" comment as in our subversion hierarchy its not *above* > and the only way it can find it is by downloading/installing in your > local repo in the usual manner - unless you've put i

Re: Using maven 2 on non-MSFT platform to build JEXL

2009-12-08 Thread Dennis Lundberg
henrib wrote: > To be complete, the site is generated ok when the commons-parent pom is just > above jexl's trunk with parent parent version 12. But then the rc publishing > fails later when the site is regenerated from what was published (lacking > the parent pom above.) > > Seems to me this is r

Re: Using maven 2 on non-MSFT platform to build JEXL

2009-12-08 Thread henrib
If it is styled in Blue - as the Jexl 1.0 site looks - and if you have the menu for reports (cobertura, etc), then you're good and I'm doing something totally stupid on my end. If site is styled in Red, no menu for reports, then we look at the same problem. Thanks for checking. Cheers, Henrib S

Re: Using maven 2 on non-MSFT platform to build JEXL

2009-12-08 Thread Niall Pemberton
On Tue, Dec 8, 2009 at 8:10 PM, henrib wrote: > > To be complete, the site is generated ok when the commons-parent pom is just > above jexl's trunk with parent parent version 12. But then the rc publishing > fails later when the site is regenerated from what was published (lacking > the parent pom

Re: Using maven 2 on non-MSFT platform to build JEXL

2009-12-08 Thread Siegfried Goeschl
Hi folks, just generated the site on Mac OS 10.4 and it looks good - the site says it it 2.0-SNAPSHOT (is this correct)? Cheers, Siegfried Goeschl henrib wrote: > No, that does not change the output. > But with a parent pom version 11, it looks ok. > > > Niall Pemberton wrote: > >> ... >> D

Re: Using maven 2 on non-MSFT platform to build JEXL

2009-12-08 Thread henrib
To be complete, the site is generated ok when the commons-parent pom is just above jexl's trunk with parent parent version 12. But then the rc publishing fails later when the site is regenerated from what was published (lacking the parent pom above.) Seems to me this is related to the getRelative

Re: Using maven 2 on non-MSFT platform to build JEXL

2009-12-08 Thread henrib
No, that does not change the output. But with a parent pom version 11, it looks ok. Niall Pemberton wrote: > > ... > Does it make any difference if you remove the leading slash from the > href="/...html" attribute on the elements in site.xml? > ... > -- View this message in context: http:/

Re: Using maven 2 on non-MSFT platform to build JEXL

2009-12-08 Thread Niall Pemberton
On Tue, Dec 8, 2009 at 4:55 PM, henrib wrote: > > I've been fighting with the JEXL environment (on a Mac) to get it to generate > an 'mvn site' correctly; in particular, the reports are not included and the > css are wrong. > > I duplicated the same env on the Mac and on a Windows box, clean from