You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Daniel Florey <da...@web.de> on 2004/10/09 13:28:20 UTC
Javadoc plugin problems
Hi folks,
I've added a component (i18n) to the commons sandbox and am using Maven for
the first time.
Everything worked fine as I used a working template from another component
(transactions). Everything, but...
I don't get managed to create the javadocs. As no one on the commons list
could help me I now try this list.
I don't know much about Maven and so I don't want to post a bug report
before making sure that the fault is not me.
As far as I've seen everything works fine (jar get created, site gets also
created) but the javadoc plugin is not able to find the sources. I've
upgraded my Maven to javadoc plugin 1.7 as I've found some similar bug
report, but this didn't help much. Still no javadocs.
Can anyone have a short look at this problem? Would be really great as I
don't have a clue how to proceed.
You can find the project in the jakarta-commons-sandbox repository, folder
i18n.
Many thanks...
BTW: In another component that I prepare for sandbox Maven creates the
javadocs but leaves out the root directory of my package. Very strange...
Thanks+regards,
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: AW: Javadoc plugin problems
Posted by Arnaud HERITIER <ah...@gmail.com>.
That's right Brett,
The javadoc package doesn't need the final '.*' because it is automatically appended.
The package defined in the POM of the sandbox-build is erroneous.
<package>org.apache.commons.${pom.artifactId.substring(8)}.*</package>
Must be replaced by :
<package>org.apache.commons.${pom.artifactId.substring(8)}</package>
Arnaud
> -----Message d'origine-----
> De : Brett Porter [mailto:brett@apache.org]
> Envoyé : dimanche 10 octobre 2004 01:51
> À : Maven Developers List
> Objet : Re: AW: Javadoc plugin problems
>
> Hi Daniel,
>
> The package you specified is org.apache.commons.i18n; whereas the shared
> build effectively makes that org.apache.commons.i18n.*. Explicitly
> specifying org.apache.commons.i18n.* in the current project also does
> not work.
>
> I don't think the package element needs/is meant to have a .* on the
> end, at least not with recent versions of the javadoc plugin. Might be
> worth suggesting this to whoever is maintaing the commons build these days?
>
> Cheers,
> Brett
>
> Daniel Florey wrote:
>
> >Hi Arnaud,
> >The problem seems to be fixed by adding the package-element to the
> >project.xml (don't know why...) This is funny as this tag is not existing at
> >other sandbox projects that generate the javadoc correctly.
> >Still the generated site seems to be broken as the style is missing.
> >Many thanks for your help,
> >Daniel
> >
> >
> >
> >>-----Ursprngliche Nachricht-----
> >>Von: dev-return-31373-daniel.florey=web.de@maven.apache.org [mailto:dev-
> >>return-31373-daniel.florey=web.de@maven.apache.org] Im Auftrag von Arnaud
> >>HERITIER
> >>Gesendet: Samstag, 9. Oktober 2004 17:58
> >>An: 'Maven Developers List'
> >>Betreff: RE: Javadoc plugin problems
> >>
> >>Hi Daniel,
> >>
> >> I'll take a look at your problem.
> >>
> >>Arnaud
> >>
> >>
> >>
> >>
> >>
> >>>-----Message d'origine-----
> >>>De : daniel.florey@web.de [mailto:daniel.florey@web.de]
> >>>Envoy : samedi 9 octobre 2004 13:28
> >>> : dev@maven.apache.org
> >>>Objet : Javadoc plugin problems
> >>>
> >>>Hi folks,
> >>>I've added a component (i18n) to the commons sandbox and am using Maven
> >>>
> >>>
> >>for
> >>
> >>
> >>>the first time.
> >>>Everything worked fine as I used a working template from another
> >>>
> >>>
> >>component
> >>
> >>
> >>>(transactions). Everything, but...
> >>>I don't get managed to create the javadocs. As no one on the commons
> >>>
> >>>
> >>list
> >>
> >>
> >>>could help me I now try this list.
> >>>I don't know much about Maven and so I don't want to post a bug report
> >>>before making sure that the fault is not me.
> >>>As far as I've seen everything works fine (jar get created, site gets
> >>>
> >>>
> >>also
> >>
> >>
> >>>created) but the javadoc plugin is not able to find the sources. I've
> >>>upgraded my Maven to javadoc plugin 1.7 as I've found some similar bug
> >>>report, but this didn't help much. Still no javadocs.
> >>>Can anyone have a short look at this problem? Would be really great as I
> >>>don't have a clue how to proceed.
> >>>You can find the project in the jakarta-commons-sandbox repository,
> >>>
> >>>
> >>folder
> >>
> >>
> >>>i18n.
> >>>Many thanks...
> >>>BTW: In another component that I prepare for sandbox Maven creates the
> >>>javadocs but leaves out the root directory of my package. Very
> >>>
> >>>
> >>strange...
> >>
> >>
> >>>Thanks+regards,
> >>>Daniel
> >>>
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>>
> >>>
> >>>#================== gPopper Menu ===================#
> >>>Delete from Gmail inbox: mailto:del|ff7d7257c86c701@gPopper
> >>>Mark message as unread: mailto:unr|ff7d7257c86c701@gPopper
> >>>Mark message as read: mailto:rea|ff7d7257c86c701@gPopper
> >>>
> >>>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> #================== gPopper Menu ===================#
> Delete from Gmail inbox: mailto:del|ff801bac5240181@gPopper
> Mark message as unread: mailto:unr|ff801bac5240181@gPopper
> Mark message as read: mailto:rea|ff801bac5240181@gPopper
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: AW: Javadoc plugin problems
Posted by Arnaud HERITIER <ah...@gmail.com>.
That's right Brett,
The javadoc package doesn't need the final '.*' because it is automatically appended.
The package defined in the POM of the sandbox-build is erroneous.
<package>org.apache.commons.${pom.artifactId.substring(8)}.*</package>
Must be replaced by :
<package>org.apache.commons.${pom.artifactId.substring(8)}</package>
Arnaud
> -----Message d'origine-----
> De : Brett Porter [mailto:brett@apache.org]
> Envoyé : dimanche 10 octobre 2004 01:51
> À : Maven Developers List
> Objet : Re: AW: Javadoc plugin problems
>
> Hi Daniel,
>
> The package you specified is org.apache.commons.i18n; whereas the shared
> build effectively makes that org.apache.commons.i18n.*. Explicitly
> specifying org.apache.commons.i18n.* in the current project also does
> not work.
>
> I don't think the package element needs/is meant to have a .* on the
> end, at least not with recent versions of the javadoc plugin. Might be
> worth suggesting this to whoever is maintaing the commons build these days?
>
> Cheers,
> Brett
>
> Daniel Florey wrote:
>
> >Hi Arnaud,
> >The problem seems to be fixed by adding the package-element to the
> >project.xml (don't know why...) This is funny as this tag is not existing at
> >other sandbox projects that generate the javadoc correctly.
> >Still the generated site seems to be broken as the style is missing.
> >Many thanks for your help,
> >Daniel
> >
> >
> >
> >>-----Ursprngliche Nachricht-----
> >>Von: dev-return-31373-daniel.florey=web.de@maven.apache.org [mailto:dev-
> >>return-31373-daniel.florey=web.de@maven.apache.org] Im Auftrag von Arnaud
> >>HERITIER
> >>Gesendet: Samstag, 9. Oktober 2004 17:58
> >>An: 'Maven Developers List'
> >>Betreff: RE: Javadoc plugin problems
> >>
> >>Hi Daniel,
> >>
> >> I'll take a look at your problem.
> >>
> >>Arnaud
> >>
> >>
> >>
> >>
> >>
> >>>-----Message d'origine-----
> >>>De : daniel.florey@web.de [mailto:daniel.florey@web.de]
> >>>Envoy : samedi 9 octobre 2004 13:28
> >>> : dev@maven.apache.org
> >>>Objet : Javadoc plugin problems
> >>>
> >>>Hi folks,
> >>>I've added a component (i18n) to the commons sandbox and am using Maven
> >>>
> >>>
> >>for
> >>
> >>
> >>>the first time.
> >>>Everything worked fine as I used a working template from another
> >>>
> >>>
> >>component
> >>
> >>
> >>>(transactions). Everything, but...
> >>>I don't get managed to create the javadocs. As no one on the commons
> >>>
> >>>
> >>list
> >>
> >>
> >>>could help me I now try this list.
> >>>I don't know much about Maven and so I don't want to post a bug report
> >>>before making sure that the fault is not me.
> >>>As far as I've seen everything works fine (jar get created, site gets
> >>>
> >>>
> >>also
> >>
> >>
> >>>created) but the javadoc plugin is not able to find the sources. I've
> >>>upgraded my Maven to javadoc plugin 1.7 as I've found some similar bug
> >>>report, but this didn't help much. Still no javadocs.
> >>>Can anyone have a short look at this problem? Would be really great as I
> >>>don't have a clue how to proceed.
> >>>You can find the project in the jakarta-commons-sandbox repository,
> >>>
> >>>
> >>folder
> >>
> >>
> >>>i18n.
> >>>Many thanks...
> >>>BTW: In another component that I prepare for sandbox Maven creates the
> >>>javadocs but leaves out the root directory of my package. Very
> >>>
> >>>
> >>strange...
> >>
> >>
> >>>Thanks+regards,
> >>>Daniel
> >>>
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>>
> >>>
> >>>#================== gPopper Menu ===================#
> >>>Delete from Gmail inbox: mailto:del|ff7d7257c86c701@gPopper
> >>>Mark message as unread: mailto:unr|ff7d7257c86c701@gPopper
> >>>Mark message as read: mailto:rea|ff7d7257c86c701@gPopper
> >>>
> >>>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> #================== gPopper Menu ===================#
> Delete from Gmail inbox: mailto:del|ff801bac5240181@gPopper
> Mark message as unread: mailto:unr|ff801bac5240181@gPopper
> Mark message as read: mailto:rea|ff801bac5240181@gPopper
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: AW: Javadoc plugin problems
Posted by Brett Porter <br...@apache.org>.
Hi Daniel,
The package you specified is org.apache.commons.i18n; whereas the shared
build effectively makes that org.apache.commons.i18n.*. Explicitly
specifying org.apache.commons.i18n.* in the current project also does
not work.
I don't think the package element needs/is meant to have a .* on the
end, at least not with recent versions of the javadoc plugin. Might be
worth suggesting this to whoever is maintaing the commons build these days?
Cheers,
Brett
Daniel Florey wrote:
>Hi Arnaud,
>The problem seems to be fixed by adding the package-element to the
>project.xml (don't know why...) This is funny as this tag is not existing at
>other sandbox projects that generate the javadoc correctly.
>Still the generated site seems to be broken as the style is missing.
>Many thanks for your help,
>Daniel
>
>
>
>>-----Ursprüngliche Nachricht-----
>>Von: dev-return-31373-daniel.florey=web.de@maven.apache.org [mailto:dev-
>>return-31373-daniel.florey=web.de@maven.apache.org] Im Auftrag von Arnaud
>>HERITIER
>>Gesendet: Samstag, 9. Oktober 2004 17:58
>>An: 'Maven Developers List'
>>Betreff: RE: Javadoc plugin problems
>>
>>Hi Daniel,
>>
>> I'll take a look at your problem.
>>
>>Arnaud
>>
>>
>>
>>
>>
>>>-----Message d'origine-----
>>>De : daniel.florey@web.de [mailto:daniel.florey@web.de]
>>>Envoyé : samedi 9 octobre 2004 13:28
>>>À : dev@maven.apache.org
>>>Objet : Javadoc plugin problems
>>>
>>>Hi folks,
>>>I've added a component (i18n) to the commons sandbox and am using Maven
>>>
>>>
>>for
>>
>>
>>>the first time.
>>>Everything worked fine as I used a working template from another
>>>
>>>
>>component
>>
>>
>>>(transactions). Everything, but...
>>>I don't get managed to create the javadocs. As no one on the commons
>>>
>>>
>>list
>>
>>
>>>could help me I now try this list.
>>>I don't know much about Maven and so I don't want to post a bug report
>>>before making sure that the fault is not me.
>>>As far as I've seen everything works fine (jar get created, site gets
>>>
>>>
>>also
>>
>>
>>>created) but the javadoc plugin is not able to find the sources. I've
>>>upgraded my Maven to javadoc plugin 1.7 as I've found some similar bug
>>>report, but this didn't help much. Still no javadocs.
>>>Can anyone have a short look at this problem? Would be really great as I
>>>don't have a clue how to proceed.
>>>You can find the project in the jakarta-commons-sandbox repository,
>>>
>>>
>>folder
>>
>>
>>>i18n.
>>>Many thanks...
>>>BTW: In another component that I prepare for sandbox Maven creates the
>>>javadocs but leaves out the root directory of my package. Very
>>>
>>>
>>strange...
>>
>>
>>>Thanks+regards,
>>>Daniel
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>>
>>>#================== gPopper Menu ===================#
>>>Delete from Gmail inbox: mailto:del|ff7d7257c86c701@gPopper
>>>Mark message as unread: mailto:unr|ff7d7257c86c701@gPopper
>>>Mark message as read: mailto:rea|ff7d7257c86c701@gPopper
>>>
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
AW: Javadoc plugin problems
Posted by Daniel Florey <da...@web.de>.
Hi Arnaud,
The problem seems to be fixed by adding the package-element to the
project.xml (don't know why...) This is funny as this tag is not existing at
other sandbox projects that generate the javadoc correctly.
Still the generated site seems to be broken as the style is missing.
Many thanks for your help,
Daniel
> -----Ursprüngliche Nachricht-----
> Von: dev-return-31373-daniel.florey=web.de@maven.apache.org [mailto:dev-
> return-31373-daniel.florey=web.de@maven.apache.org] Im Auftrag von Arnaud
> HERITIER
> Gesendet: Samstag, 9. Oktober 2004 17:58
> An: 'Maven Developers List'
> Betreff: RE: Javadoc plugin problems
>
> Hi Daniel,
>
> I'll take a look at your problem.
>
> Arnaud
>
>
>
> > -----Message d'origine-----
> > De : daniel.florey@web.de [mailto:daniel.florey@web.de]
> > Envoyé : samedi 9 octobre 2004 13:28
> > À : dev@maven.apache.org
> > Objet : Javadoc plugin problems
> >
> > Hi folks,
> > I've added a component (i18n) to the commons sandbox and am using Maven
> for
> > the first time.
> > Everything worked fine as I used a working template from another
> component
> > (transactions). Everything, but...
> > I don't get managed to create the javadocs. As no one on the commons
> list
> > could help me I now try this list.
> > I don't know much about Maven and so I don't want to post a bug report
> > before making sure that the fault is not me.
> > As far as I've seen everything works fine (jar get created, site gets
> also
> > created) but the javadoc plugin is not able to find the sources. I've
> > upgraded my Maven to javadoc plugin 1.7 as I've found some similar bug
> > report, but this didn't help much. Still no javadocs.
> > Can anyone have a short look at this problem? Would be really great as I
> > don't have a clue how to proceed.
> > You can find the project in the jakarta-commons-sandbox repository,
> folder
> > i18n.
> > Many thanks...
> > BTW: In another component that I prepare for sandbox Maven creates the
> > javadocs but leaves out the root directory of my package. Very
> strange...
> >
> > Thanks+regards,
> > Daniel
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> >
> > #================== gPopper Menu ===================#
> > Delete from Gmail inbox: mailto:del|ff7d7257c86c701@gPopper
> > Mark message as unread: mailto:unr|ff7d7257c86c701@gPopper
> > Mark message as read: mailto:rea|ff7d7257c86c701@gPopper
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Javadoc plugin problems
Posted by Arnaud HERITIER <ah...@gmail.com>.
Hi Daniel,
I'll take a look at your problem.
Arnaud
> -----Message d'origine-----
> De : daniel.florey@web.de [mailto:daniel.florey@web.de]
> Envoyé : samedi 9 octobre 2004 13:28
> À : dev@maven.apache.org
> Objet : Javadoc plugin problems
>
> Hi folks,
> I've added a component (i18n) to the commons sandbox and am using Maven for
> the first time.
> Everything worked fine as I used a working template from another component
> (transactions). Everything, but...
> I don't get managed to create the javadocs. As no one on the commons list
> could help me I now try this list.
> I don't know much about Maven and so I don't want to post a bug report
> before making sure that the fault is not me.
> As far as I've seen everything works fine (jar get created, site gets also
> created) but the javadoc plugin is not able to find the sources. I've
> upgraded my Maven to javadoc plugin 1.7 as I've found some similar bug
> report, but this didn't help much. Still no javadocs.
> Can anyone have a short look at this problem? Would be really great as I
> don't have a clue how to proceed.
> You can find the project in the jakarta-commons-sandbox repository, folder
> i18n.
> Many thanks...
> BTW: In another component that I prepare for sandbox Maven creates the
> javadocs but leaves out the root directory of my package. Very strange...
>
> Thanks+regards,
> Daniel
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> #================== gPopper Menu ===================#
> Delete from Gmail inbox: mailto:del|ff7d7257c86c701@gPopper
> Mark message as unread: mailto:unr|ff7d7257c86c701@gPopper
> Mark message as read: mailto:rea|ff7d7257c86c701@gPopper
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org