You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jeff Jensen <je...@upstairstechnology.com> on 2006/02/07 21:39:55 UTC
[m1.1b2] Javadoc plugin 1.8 warnings report is empty
Hi,
Our Javadoc Warnings Report run with maven site has failed for along time. I
finally have time to (hopefully!) resolve the problem.
The report will state the number of files, number of errors=0, and an empty
Files section.
Running it with maven.javadoc.debug=true, the following info is in the log (the
first error message):
Read 276 line(s) from input file
Building map from 276 input line(s)
Parsing line [javadoc]
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
us.state.vantage.hm.ar.entity.AccountAWPContainer
*** WARNING: exception parsing line ' [javadoc]
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
us.state.vantage.hm.ar.entity.AccountAWPContainer':
org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
java.lang.NoSuchMethodError:
org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
at
org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarningsTextToXml.java:295)
This failure repeats many times, I think for every warning in the file.
But, if I run "maven javadoc xdoc" only, the file parses correctly.
Nothing is obvious to me at this point - I keep reviewing the jelly file hoping
to find something. Does it to anyone else?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m1.1b2] Javadoc plugin 1.8 warnings report is empty
Posted by Arnaud HERITIER <ah...@gmail.com>.
Hi Jeff,
I posted a comment on the issue you opened.
I don't know which plugins use the bad release of the commons-collection.
Can you attach to the issue the list of your plugins (maven -i)
Can you try the last snapshot of maven 1.1 beta 3 :
http://people.apache.org/~aheritier/maven/1.X/snapshots/
cheers
Arnaud
On 2/8/06, Jeff Jensen <je...@upstairstechnology.com> wrote:
> Hi Arnaud, thanks for the info. Are there any particular plugins I can back
> down a rev on so that it works?
>
>
> -----Original Message-----
> From: Arnaud HERITIER [mailto:aheritier@gmail.com]
> Sent: Tuesday, February 07, 2006 5:07 PM
> To: Maven Users List
> Subject: Re: [m1.1b2] Javadoc plugin 1.8 warnings report is empty
>
> It's a problem of conflict between different plugins which uses two
> incopatible releases of commons-collections.
> It'll be fixed in maven 1.1 beta 3 because we unified all the dependencies.
>
> Arnaud
>
> On 2/7/06, Jeff Jensen <je...@upstairstechnology.com> wrote:
> > Hello Lukas! Thank you for the prompt reply and interest to help :-)
> >
> > Yes, you did! I know it worked for awhile, I am not sure when/how it
> > broke again. I only know it has been broken for awhile.
> >
> > This is a different problem this time, and it exists across all 4 of
> > our projects (the small and large).
> >
> > I will gladly create that JIRA next...
> > I will first create it with all the details I can, then try to make a
> > small test case.
> >
> >
> > Quoting Lukas Theussl <lt...@apache.org>:
> >
> > > Hi Jeff,
> > >
> > > I thought we had resolved all your problems with javadoc warnings ;)
> > >
> > > Would you mind opening another issue with more detailed information,
> > > ie the exact versions of javadoc, xdoc and site plugin that you are
> > > using, and the files that are generated in target/javadoc? Or even
> > > better, a small, reproducible test case? It's weird though that it
> > > works with xdoc but not with site.
> > >
> > > Thanks,
> > > Lukas
> > >
> > >
> > > Jeff Jensen wrote:
> > > > Hi,
> > > >
> > > > Our Javadoc Warnings Report run with maven site has failed for along
> time.
> > > I
> > > > finally have time to (hopefully!) resolve the problem.
> > > >
> > > > The report will state the number of files, number of errors=0, and
> > > > an empty Files section.
> > > >
> > > > Running it with maven.javadoc.debug=true, the following info is in
> > > > the log
> > > (the
> > > > first error message):
> > > >
> > > > Read 276 line(s) from input file
> > > > Building map from 276 input line(s)
> > > > Parsing line [javadoc]
> > > >
> > >
> >
> C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccount
> AWPContainer.java:66:
> > > > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > > > us.state.vantage.hm.ar.entity.AccountAWPContainer
> > > > *** WARNING: exception parsing line ' [javadoc]
> > > >
> > >
> >
> C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccount
> AWPContainer.java:66:
> > > > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > > > us.state.vantage.hm.ar.entity.AccountAWPContainer':
> > > >
> > >
> > org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Lja
> > va/util/Set;
> > > > java.lang.NoSuchMethodError:
> > > >
> > >
> > org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Lja
> > va/util/Set;
> > > > at
> > > >
> > >
> > org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarn
> > ingsTextToXml.java:295)
> > > >
> > > >
> > > > This failure repeats many times, I think for every warning in the
> file.
> > > >
> > > >
> > > > But, if I run "maven javadoc xdoc" only, the file parses correctly.
> > > >
> > > > Nothing is obvious to me at this point - I keep reviewing the
> > > > jelly file
> > > hoping
> > > > to find something. Does it to anyone else?
> > > >
> > > >
> > > > ------------------------------------------------------------------
> > > > --- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [m1.1b2] Javadoc plugin 1.8 warnings report is empty
Posted by Jeff Jensen <je...@upstairstechnology.com>.
Hi Arnaud, thanks for the info. Are there any particular plugins I can back
down a rev on so that it works?
-----Original Message-----
From: Arnaud HERITIER [mailto:aheritier@gmail.com]
Sent: Tuesday, February 07, 2006 5:07 PM
To: Maven Users List
Subject: Re: [m1.1b2] Javadoc plugin 1.8 warnings report is empty
It's a problem of conflict between different plugins which uses two
incopatible releases of commons-collections.
It'll be fixed in maven 1.1 beta 3 because we unified all the dependencies.
Arnaud
On 2/7/06, Jeff Jensen <je...@upstairstechnology.com> wrote:
> Hello Lukas! Thank you for the prompt reply and interest to help :-)
>
> Yes, you did! I know it worked for awhile, I am not sure when/how it
> broke again. I only know it has been broken for awhile.
>
> This is a different problem this time, and it exists across all 4 of
> our projects (the small and large).
>
> I will gladly create that JIRA next...
> I will first create it with all the details I can, then try to make a
> small test case.
>
>
> Quoting Lukas Theussl <lt...@apache.org>:
>
> > Hi Jeff,
> >
> > I thought we had resolved all your problems with javadoc warnings ;)
> >
> > Would you mind opening another issue with more detailed information,
> > ie the exact versions of javadoc, xdoc and site plugin that you are
> > using, and the files that are generated in target/javadoc? Or even
> > better, a small, reproducible test case? It's weird though that it
> > works with xdoc but not with site.
> >
> > Thanks,
> > Lukas
> >
> >
> > Jeff Jensen wrote:
> > > Hi,
> > >
> > > Our Javadoc Warnings Report run with maven site has failed for along
time.
> > I
> > > finally have time to (hopefully!) resolve the problem.
> > >
> > > The report will state the number of files, number of errors=0, and
> > > an empty Files section.
> > >
> > > Running it with maven.javadoc.debug=true, the following info is in
> > > the log
> > (the
> > > first error message):
> > >
> > > Read 276 line(s) from input file
> > > Building map from 276 input line(s)
> > > Parsing line [javadoc]
> > >
> >
>
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccount
AWPContainer.java:66:
> > > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > > us.state.vantage.hm.ar.entity.AccountAWPContainer
> > > *** WARNING: exception parsing line ' [javadoc]
> > >
> >
>
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccount
AWPContainer.java:66:
> > > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > > us.state.vantage.hm.ar.entity.AccountAWPContainer':
> > >
> >
> org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Lja
> va/util/Set;
> > > java.lang.NoSuchMethodError:
> > >
> >
> org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Lja
> va/util/Set;
> > > at
> > >
> >
> org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarn
> ingsTextToXml.java:295)
> > >
> > >
> > > This failure repeats many times, I think for every warning in the
file.
> > >
> > >
> > > But, if I run "maven javadoc xdoc" only, the file parses correctly.
> > >
> > > Nothing is obvious to me at this point - I keep reviewing the
> > > jelly file
> > hoping
> > > to find something. Does it to anyone else?
> > >
> > >
> > > ------------------------------------------------------------------
> > > --- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m1.1b2] Javadoc plugin 1.8 warnings report is empty
Posted by Arnaud HERITIER <ah...@gmail.com>.
It's a problem of conflict between different plugins which uses two
incopatible releases of commons-collections.
It'll be fixed in maven 1.1 beta 3 because we unified all the dependencies.
Arnaud
On 2/7/06, Jeff Jensen <je...@upstairstechnology.com> wrote:
> Hello Lukas! Thank you for the prompt reply and interest to help :-)
>
> Yes, you did! I know it worked for awhile, I am not sure when/how it broke
> again. I only know it has been broken for awhile.
>
> This is a different problem this time, and it exists across all 4 of our
> projects (the small and large).
>
> I will gladly create that JIRA next...
> I will first create it with all the details I can, then try to make a small test
> case.
>
>
> Quoting Lukas Theussl <lt...@apache.org>:
>
> > Hi Jeff,
> >
> > I thought we had resolved all your problems with javadoc warnings ;)
> >
> > Would you mind opening another issue with more detailed information, ie
> > the exact versions of javadoc, xdoc and site plugin that you are using,
> > and the files that are generated in target/javadoc? Or even better, a
> > small, reproducible test case? It's weird though that it works with xdoc
> > but not with site.
> >
> > Thanks,
> > Lukas
> >
> >
> > Jeff Jensen wrote:
> > > Hi,
> > >
> > > Our Javadoc Warnings Report run with maven site has failed for along time.
> > I
> > > finally have time to (hopefully!) resolve the problem.
> > >
> > > The report will state the number of files, number of errors=0, and an empty
> > > Files section.
> > >
> > > Running it with maven.javadoc.debug=true, the following info is in the log
> > (the
> > > first error message):
> > >
> > > Read 276 line(s) from input file
> > > Building map from 276 input line(s)
> > > Parsing line [javadoc]
> > >
> >
> C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
> > > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > > us.state.vantage.hm.ar.entity.AccountAWPContainer
> > > *** WARNING: exception parsing line ' [javadoc]
> > >
> >
> C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
> > > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > > us.state.vantage.hm.ar.entity.AccountAWPContainer':
> > >
> >
> org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
> > > java.lang.NoSuchMethodError:
> > >
> >
> org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
> > > at
> > >
> >
> org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarningsTextToXml.java:295)
> > >
> > >
> > > This failure repeats many times, I think for every warning in the file.
> > >
> > >
> > > But, if I run "maven javadoc xdoc" only, the file parses correctly.
> > >
> > > Nothing is obvious to me at this point - I keep reviewing the jelly file
> > hoping
> > > to find something. Does it to anyone else?
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m1.1b2] Javadoc plugin 1.8 warnings report is empty
Posted by Jeff Jensen <je...@upstairstechnology.com>.
Hello Lukas! Thank you for the prompt reply and interest to help :-)
Yes, you did! I know it worked for awhile, I am not sure when/how it broke
again. I only know it has been broken for awhile.
This is a different problem this time, and it exists across all 4 of our
projects (the small and large).
I will gladly create that JIRA next...
I will first create it with all the details I can, then try to make a small test
case.
Quoting Lukas Theussl <lt...@apache.org>:
> Hi Jeff,
>
> I thought we had resolved all your problems with javadoc warnings ;)
>
> Would you mind opening another issue with more detailed information, ie
> the exact versions of javadoc, xdoc and site plugin that you are using,
> and the files that are generated in target/javadoc? Or even better, a
> small, reproducible test case? It's weird though that it works with xdoc
> but not with site.
>
> Thanks,
> Lukas
>
>
> Jeff Jensen wrote:
> > Hi,
> >
> > Our Javadoc Warnings Report run with maven site has failed for along time.
> I
> > finally have time to (hopefully!) resolve the problem.
> >
> > The report will state the number of files, number of errors=0, and an empty
> > Files section.
> >
> > Running it with maven.javadoc.debug=true, the following info is in the log
> (the
> > first error message):
> >
> > Read 276 line(s) from input file
> > Building map from 276 input line(s)
> > Parsing line [javadoc]
> >
>
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
> > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > us.state.vantage.hm.ar.entity.AccountAWPContainer
> > *** WARNING: exception parsing line ' [javadoc]
> >
>
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
> > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > us.state.vantage.hm.ar.entity.AccountAWPContainer':
> >
>
org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
> > java.lang.NoSuchMethodError:
> >
>
org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
> > at
> >
>
org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarningsTextToXml.java:295)
> >
> >
> > This failure repeats many times, I think for every warning in the file.
> >
> >
> > But, if I run "maven javadoc xdoc" only, the file parses correctly.
> >
> > Nothing is obvious to me at this point - I keep reviewing the jelly file
> hoping
> > to find something. Does it to anyone else?
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m1.1b2] Javadoc plugin 1.8 warnings report is empty
Posted by Lukas Theussl <lt...@apache.org>.
Hi Jeff,
I thought we had resolved all your problems with javadoc warnings ;)
Would you mind opening another issue with more detailed information, ie
the exact versions of javadoc, xdoc and site plugin that you are using,
and the files that are generated in target/javadoc? Or even better, a
small, reproducible test case? It's weird though that it works with xdoc
but not with site.
Thanks,
Lukas
Jeff Jensen wrote:
> Hi,
>
> Our Javadoc Warnings Report run with maven site has failed for along time. I
> finally have time to (hopefully!) resolve the problem.
>
> The report will state the number of files, number of errors=0, and an empty
> Files section.
>
> Running it with maven.javadoc.debug=true, the following info is in the log (the
> first error message):
>
> Read 276 line(s) from input file
> Building map from 276 input line(s)
> Parsing line [javadoc]
> C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
> warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> us.state.vantage.hm.ar.entity.AccountAWPContainer
> *** WARNING: exception parsing line ' [javadoc]
> C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
> warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> us.state.vantage.hm.ar.entity.AccountAWPContainer':
> org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
> java.lang.NoSuchMethodError:
> org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
> at
> org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarningsTextToXml.java:295)
>
>
> This failure repeats many times, I think for every warning in the file.
>
>
> But, if I run "maven javadoc xdoc" only, the file parses correctly.
>
> Nothing is obvious to me at this point - I keep reviewing the jelly file hoping
> to find something. Does it to anyone else?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org