Arnaud, The javadoc warnings report is working fine with Beta3 for me.
Thanks for all the help, Girish On 12/11/05, Jeff Jensen <[EMAIL PROTECTED]> wrote: > > Thanks - the beta 3 snapshot downloaded from your site does not fix the > Javadoc parsing problem. I have updated notes here on that: > > http://jira.codehaus.org/browse/MPJAVADOC-61 > > > -----Original Message----- > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: Saturday, December 10, 2005 5:53 PM > To: Maven Users List > Subject: Re: [m1] Re: Javadoc warnings report is not getting generated > with > Maven 1.1 beta1 and beta2 > > thanks. > > You can download a snapshot of maven 1.1 beta 3 (zip archive only) here : > http://people.apache.org/~aheritier/maven/1.X/snapshots/ > <http://people.apache.org/%7Eaheritier/maven/1.X/snapshots/> > > Arnaud > > On 12/11/05, Jeff Jensen <[EMAIL PROTECTED]> wrote: > > > > Hi Arnaud, > > Thank you for looking at this. > > > > This issue has the log attachment: > > http://jira.codehaus.org/browse/MAVEN-1733 > > > > Looking forward to trying the latest build! > > > > > > -----Original Message----- > > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > > Sent: Saturday, December 10, 2005 3:04 PM > > To: Maven Users List > > Subject: Re: [m1] Re: Javadoc warnings report is not getting generated > > with Maven 1.1 beta1 and beta2 > > > > Hi all, > > > > Girish, I'm sorry, I didn't see your first mail. > > > > The error " org.apache.commons.collections.set.ListOrderedSet: method > > <init>()V not found" comes from an incompability between two commons > > collections releases : > > http://jakarta.apache.org/commons/collections/compatibility.html > > > > As we share the classloader between the core and the plugins we had > > some issues due to this incompability. > > > > I cleaned up all our dependencies and it should fix this problem. > > > > I'll upload a SNAPSHOT of maven beta 3 in some hours. > > > > For the bootstrap problem, can you send me the log or open an issue > > please. > > > > Arnaud > > > > > > On 12/10/05, Jeff Jensen < [EMAIL PROTECTED]> wrote: > > > > > > Lukas, > > > > > > Sorry, beta 3 doesn't solve it for me. I could not bootstrap build > > > (see error below), but did a "use maven to build maven". > > > > > > I also: > > > - cleared out my local repo so all plugins were re-downloaded > > > - tried it with and without a javadoc-1.8-SNAPSHOT dependency > > > > > > > > > I may have found a clue, if not the culprit, though. I think it > > > crashes while trying to parse this entry in the report.txt file: > > > > > > [javadoc] > > > > > > C:\devroot\customers\dhs\perforce\healthmatchbatch\main\src\java\us\ > > > st > > > ate\va > > > ntage\hm\batch\ar\policy\premiumcreator\package.html: warning - Tag > > @link: > > > reference not found: > us.state.vantage.hm.batch.ar.policy.premiumcreator. > > > [javadoc] PremiumCreatorStrategyCredit > > > > > > > > > Note that the FQCL wraps to the next line. Perhaps this is the > > > parse error?? Can it handle that in your sandbox? > > > > > > > > > Bootstrap error: > > > > > > [exec] [delete] Deleting directory > > > > > > C:\devroot\reference\maven\maven-1\plugins\trunk\genapp\src\plugin-t > > > es > > > t\temp > > > latesTest\target > > > > > > [exec] BUILD FAILED > > > [exec] org.apache.maven.werkz.UnattainableGoalException: Unable > > > to obtain goal [plugin:test] -- file:/C:/Documents and > > > Settings/jjensen/.maven/cache/maven-plugin-plugin-1.7-SNAPSHOT > > > /plugin.jelly: > > > 499:34: <maven:maven> Unable to obtain goal [testPlugin] -- > > > > > > file:/C:/devroot/reference/maven/maven-1/core/trunk/../../plugins/tr > > > un > > > k/gena > > > pp/src/plugin-test/maven.xml:20:127: <maven:reactor> Reactor > > > subproject failure occurred > > > > > > [snip] > > > > > > [exec] Root cause > > > [exec] org.apache.maven.werkz.UnattainableGoalException: Unable > > > to obtain goal [testPlugin] -- > > > > > > file:/C:/devroot/reference/maven/maven-1/core/trunk/../../plugins/tr > > > un > > > k/gena > > > pp/src/plugin-test/maven.xml:20:127: <maven:reactor> Reactor > > > subproject failure occurred > > > [exec] at org.apache.maven.werkz.Goal.fire (Goal.java:663) > > > > > > > > > I would prefer nightly build snapshots, but I don't think Maven does > > > that nor could I find any... > > > > > > > > > -----Original Message----- > > > From: Lukas Theussl [mailto:[EMAIL PROTECTED] > > > Sent: Saturday, December 10, 2005 10:37 AM > > > To: Maven Users List > > > Subject: Re: [m1] Re: Javadoc warnings report is not getting > > > generated with Maven 1.1 beta1 and beta2 > > > > > > > > > > > > > Hope this gets resolved soon :-) > > > > > > Seems to be resolved already :) - see my comment on JIRA. > > > > > > -Lukas > > > > > > > > > > > > > > Thanks, > > > > Girish > > > > > > > > > > > > On 12/9/05, Lukas Theussl < [EMAIL PROTECTED]> wrote: > > > > > > > >>If it's not the same issue please open a new one. I am seeing > > > >>empty javadoc warning reports too, but I haven't had the time to > > investigate. > > > >> > > > >>-Lukas > > > >> > > > >> > > > >>Jeff Jensen wrote: > > > >> > > > >>>We miss this report for summarizing Javadoc errors. > > > >>> > > > >>>I entered this JIRA on 27/Sep/05: > > > >>> > > > >>>http://jira.codehaus.org/browse/MPJAVADOC-61 > > > >>> > > > >>>Does it apply to your situation? If so, please add your details > > > >>>to help diagnose. Your error situation may be different than mine. > > > >>>Our results > > > >> > > > >>are > > > >> > > > >>>the same though, an empty report. > > > >>> > > > >>> > > > >>>-----Original Message----- > > > >>>From: Girish Nagaraj [mailto:[EMAIL PROTECTED] > > > >>>Sent: Friday, December 09, 2005 5:07 AM > > > >>>To: [email protected] > > > >>>Subject: [m1] Re: Javadoc warnings report is not getting > > > >>>generated with Maven 1.1 beta1 and beta2 > > > >>> > > > >>>Hello All, > > > >>> > > > >>>Unfortunately I did not get any response to my email. Wonder if > > > >>>nobody > > > >> > > > >>cares > > > >> > > > >>>about the javadoc warnings report of if I am the only using the > > report. > > > >>> > > > >>>I am still seeing this problem even with a very simple single > > > >>>java file > > > >> > > > >>in > > > >> > > > >>>the project. > > > >>> > > > >>>Just add any java file which contains a javadoc warning (like no > > > >>>@param > > > >> > > > >>or > > > >> > > > >>>something like that) public class MyTest { > > > >>> /** > > > >>> ** Constructor. > > > >>> ** @param oldAttr Some error > > > >>> */ > > > >>> public MyTest(String foo, String bar) > > > >>> { > > > >>> > > > >>> } > > > >>>} > > > >>> > > > >>>Maven javadoc can be seen error out with the following warning on > > > >>>the console > > > >>> > > > >>>*** WARNING: exception parsing line ' [javadoc] > > > >>>C:\Temp\mtest\src\main\java\ora > > > >>>cle\mds\persistence\MyTest.java:20: warning - @param argument > > "oldAttr" > > > >> > > > >>is > > > >> > > > >>>not a parameter name.': > > > >> > > > >>org.apache.commons.collections.set.ListOrderedSet: > > > >> > > > >>>method <in > > > >>>it>()V not found > > > >>> > > > >>>and the javadoc warnings report contains just the number of files > > > >>>having warnings. > > > >>> > > > >>>Could somebody please suggest how to fix this problem? Is > > > >>>upgrading to > > > >> > > > >>Maven > > > >> > > > >>>2 only soln to resolve this problem :( ? > > > >>> > > > >>>Thanks > > > >>>Girish > > > >>> > > > >>> > > > >>> > > > >>>On 11/19/05, Girish Nagaraj < [EMAIL PROTECTED]> wrote: > > > >>> > > > >>> > > > >>>>Hello, > > > >>>> > > > >>>>When I run "maven site", the javadoc warnings report fails to > > > >>>>get generated correctly.It just contains the number of files, > > > >>>>but does not list the javadoc problems (though there are many). > > > >>>>The following message shows up on the console > > > >>>>*** WARNING: exception parsing line ' [javadoc] <....>.java:726: > > > >>>>warning > > > >>>>- Tag @inheritDoc cannot be used in constructor documentation. > > > >>>>It can only be used in the following types of documentation: > > > >>>>method, inline > > > >>> > > > >>>text.': > > > >>> > > > >>> > > > >>>>org.apache.commons.collections.set.ListOrderedSet: method > > > >>>><init>()V not found > > > >>>> > > > >>>>Is there anyway this I can be fix this? > > > >>>> > > > >>>>Thanks, > > > >>>>Girish > > > >>>> > > > >>> > > > >>> > > > >>> > > > >>>----------------------------------------------------------------- > > > >>>-- > > > >>>-- To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >>>For additional commands, e-mail: [EMAIL PROTECTED] > > > >>> > > > >> > > > >>------------------------------------------------------------------ > > > >>-- > > > >>- To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >>For additional commands, e-mail: [EMAIL PROTECTED] > > > >> > > > > > > > >> > > > > > > > > > > -------------------------------------------------------------------- > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > -------------------------------------------------------------------- > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
