RE : RE : RE : RE : [vote] Release Maven Site plugin 2.0-beta-5

2006-05-11 Thread Olivier Lamy
Great and big thanks. Works great.

I can add my user vote : 99E+10 ;-))

-Olivier

-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED] 
Envoyé : jeudi 11 mai 2006 10:42
À : Maven Developers List
Objet : Re: RE : RE : RE : [vote] Release Maven Site plugin 2.0-beta-5


Sorry, forgot to deploy that one. Try now.

- Brett

Olivier Lamy wrote:
> Thanks.
> But
> [INFO]
>

> [ERROR] FATAL ERROR
> [INFO]
>

> [INFO] org.apache.maven.doxia.site.decoration.Menu.isInheritAsRef()Z
> [INFO]
>

> [INFO] Trace
> java.lang.NoSuchMethodError:
> org.apache.maven.doxia.site.decoration.Menu.isInheritAsRef()Z
> at
>
org.apache.maven.plugins.site.AbstractSiteMojo.populateModules(AbstractS
> iteMojo.java:267)
> at
>
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationMod
> el(AbstractSiteRe
> nderingMojo.java:510)
> 
> -Olivier
> 
> 
> -Message d'origine-
> De : Brett Porter [mailto:[EMAIL PROTECTED]
> Envoyé : jeudi 11 mai 2006 09:31
> À : Maven Developers List
> Objet : Re: RE : RE : [vote] Release Maven Site plugin 2.0-beta-5
> 
> 
> Yes, sorry - this was down until recently too. I've deployed them 
> both.
> 
> Olivier Lamy wrote:
>> OK great and thanks.
>> What about deploy a snapshot ?
>>
>> I'm not sure but yesterday, I had the following trouble with multi
>> modules
>>
>> Root
>>   pom.xml
>> src/site/site.xml (skin stylus )
>>   module
>> pom.xml
>> src/site/site.xml (skin stylus )
>>   others modules with same structure
>>
>> I have noticed the modules not used the skin.
>> Question : do I really need to declare the skin in all modules 
>> whereas
> 
>> it's declared in the root site.xml In previous snapshot version I 
>> need
> 
>> to do it.
>>
>> - Olivier
>>
>>
>> -Message d'origine-
>> De : Brett Porter [mailto:[EMAIL PROTECTED]
>> Envoyé : jeudi 11 mai 2006 09:15
>> À : Maven Developers List
>> Objet : Re: RE : [vote] Release Maven Site plugin 2.0-beta-5
>>
>>
>> I've already fixed this, but unfortunately have not been able to
>> commit
>> as SVN is still down.
>>
>> It just needs a null check at the location of the check
>>
>> Olivier Lamy wrote:
>>> Hi,
>>> Not a maven dev but a user who made some tests ;-).
>>> Today,
>>> I made this :
>>> rm -rf $HOME/.m2/repository/*
>>> mvn -P snapshots -U clean site site:deploy (snapshots profile
>>> included
>>> snapshots in apache and codehaus)
>>>
>>>
>>> I have the stack trace :
>>> [INFO] Generate "Dependencies" report.
>>> [INFO]
>>> 
>>> -
>>> -
>>> --
>>> [ERROR] FATAL ERROR
>>> [INFO]
>>>
>> -
>> -
>> --
>>> [INFO] null
>>> [INFO]
>>>
>> -
>> -
>> --
>>> [INFO] Trace
>>> java.lang.NullPointerException
>>> at
>>>
>> org.apache.maven.report.projectinfo.ReportResolutionListener$Node.acc
>> e
>> ss
>>> $000(ReportResolu
>>> tionListener.java:149)
>>> at
>>>
>> org.apache.maven.report.projectinfo.ReportResolutionListener.manageAr
>> t
>> if
>>> act(ReportResolut
>>> ionListener.java:121)
>>> at
>>>
>> org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent
>> (
>> De
>>> faultArtifactColl
>>> ector.java:408)
>>>
>>> Glurspp ;-)
>>>
>>> In my case it's a multi module site.
>>>
>>> The root site is well generated and deployed but failed on the first

>>> module.
>>>
>>> Any idea ? (do you need more information on poms or something else ?
>>> )
>>>
>>> Thanks,
>>> -Olivier
>>>
>>>
>>> -Message d'origine-
>>> De : Brett Porter [mailto:[EMAIL PROTECTED]
>>> Envoyé : mercredi 10 mai 2006 20:21
>>> À : Maven Developers List
>>> Objet : [vote] Release Mav

Re: RE : RE : RE : [vote] Release Maven Site plugin 2.0-beta-5

2006-05-11 Thread Brett Porter

Sorry, forgot to deploy that one. Try now.

- Brett

Olivier Lamy wrote:

Thanks.
But 
[INFO]


[ERROR] FATAL ERROR
[INFO]

[INFO] org.apache.maven.doxia.site.decoration.Menu.isInheritAsRef()Z
[INFO]

[INFO] Trace
java.lang.NoSuchMethodError:
org.apache.maven.doxia.site.decoration.Menu.isInheritAsRef()Z
at
org.apache.maven.plugins.site.AbstractSiteMojo.populateModules(AbstractS
iteMojo.java:267)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationMod
el(AbstractSiteRe
nderingMojo.java:510)

-Olivier


-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED] 
Envoyé : jeudi 11 mai 2006 09:31

À : Maven Developers List
Objet : Re: RE : RE : [vote] Release Maven Site plugin 2.0-beta-5


Yes, sorry - this was down until recently too. I've deployed them both.

Olivier Lamy wrote:

OK great and thanks.
What about deploy a snapshot ?

I'm not sure but yesterday, I had the following trouble with multi 
modules


Root
  pom.xml
src/site/site.xml (skin stylus )
  module
pom.xml
src/site/site.xml (skin stylus )
  others modules with same structure

I have noticed the modules not used the skin.
Question : do I really need to declare the skin in all modules whereas



it's declared in the root site.xml In previous snapshot version I need



to do it.

- Olivier


-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 mai 2006 09:15
À : Maven Developers List
Objet : Re: RE : [vote] Release Maven Site plugin 2.0-beta-5


I've already fixed this, but unfortunately have not been able to 
commit

as SVN is still down.

It just needs a null check at the location of the check

Olivier Lamy wrote:

Hi,
Not a maven dev but a user who made some tests ;-).
Today,
I made this :
rm -rf $HOME/.m2/repository/*
mvn -P snapshots -U clean site site:deploy (snapshots profile 
included

snapshots in apache and codehaus)


I have the stack trace :
[INFO] Generate "Dependencies" report.
[INFO]
-
-
--
[ERROR] FATAL ERROR
[INFO]


--
--

[INFO] null
[INFO]


--
--

[INFO] Trace
java.lang.NullPointerException
at


org.apache.maven.report.projectinfo.ReportResolutionListener$Node.acce
ss

$000(ReportResolu
tionListener.java:149)
at


org.apache.maven.report.projectinfo.ReportResolutionListener.manageArt
if

act(ReportResolut
ionListener.java:121)
at


org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(
De

faultArtifactColl
ector.java:408)

Glurspp ;-)

In my case it's a multi module site.

The root site is well generated and deployed but failed on the first
module.

Any idea ? (do you need more information on poms or something else ? 
)


Thanks,
-Olivier


-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 mai 2006 20:21
À : Maven Developers List
Objet : [vote] Release Maven Site plugin 2.0-beta-5


Hi,

There's a wealth of new features here.

(snapshot pending svn.apache.org coming back up, also I have the docs



here to commit then too)

[ ] +1
[ ] +0
[ ] -1

http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146&styl
e
Na
me=Text&version=12541

* [MSITE-23] - problems with site:stage
* [MSITE-24] - Site deployment doesn't allow users in the group to
write

files
* [MSITE-40] - don't generate doc file if it is unchanged
* [MSITE-44] - make site reactor aware
* [MSITE-48] - add reusable skin functionality and create skins
default,

stylus and classic
* [MSITE-51] - add breadcrumbs
* [MSITE-58] - Ability to assign a report to choosen navigation menu
* [MSITE-65] - ${parentProject}\ in default site descriptor doesn't
resolve
* [MSITE-71] - Plugin uses NON interpolated model values (e.g URL)

due

to MavenProject.getParent returning non interpolated project
* [MSITE-72] - new non reactor populateModules SiteMojo code assumes 
each POM declares its own URL

* [MSITE-73] - new site code fails to generate banner images in

projects

other than site.xml owning project
* [MSITE-74] - Suport proxy
* [MSITE-86] - ${modules} macro placed in site.xml does work properly
* [MSITE-91] - "src/site/site.xml" hardcoded in AbstractSiteMojo.java
* [MSITE-97] - Site plugin doesn't copy images to target
* [MSITE-102] - SCM files in src/site directory cause 'mvn site' to
fail

- need to exclude files
* [MSITE-104] - There is no way to specify the input encoding of site



documents
* [MSITE-108] - problem with nav generation (collapse = true) 
snapshot

used 20060315.092459-4.jar   (same trouble doxia trunk)
* [MSITE-110] - Use reactor to find parent URL where