Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://jira.codehaus.org/browse/MPJAVADOC-42 Here is an overview of the issue: --------------------------------------------------------------------- Key: MPJAVADOC-42 Summary: javadoc:generate from CVS fails in some projects Type: Bug Status: Open Priority: Blocker Original Estimate: 3 hours Time Spent: Unknown Remaining: 3 hours Project: maven-javadoc-plugin Fix Fors: 1.7 Versions: 1.7 Assignee: Felipe Leme Reporter: Felipe Leme Created: Wed, 1 Sep 2004 4:56 PM Updated: Wed, 1 Sep 2004 4:56 PM Description: I'm using javadoc-1.7 from CVS and the javadoc:warning tag fails in many of our projects. Here is an example: maven-javadoc-plugin:report: [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] Loading source files for package com.cpqd.util.fileconnector... [javadoc] Loading source files for package com.cpqd.util.fileconnector.conne ctor... [javadoc] Loading source files for package XXXX [javadoc] Constructing Javadoc information... [javadoc] Copying file C:\Documents and Settings\t_fl01\.maven\cache\maven-javadoc-plugin-1.7-SNAPSHOT\plugin-resources\stylesheet.css to file S:\components\components\fileconnector\target\docs\apidocs\stylesheet.css... [javadoc] Building tree for all the packages and classes... [javadoc] Building index for all the packages and classes... [javadoc] javadoc: warning - getUserName: @return tag has no arguments. [javadoc] Building index for all classes... [javadoc] Generating S:\components\components\fileconnector\target\docs\apidocs\help-doc.html... [javadoc] 1 warning BUILD FAILED File...... C:\Documents and Settings\t_fl01\.maven\cache\maven-javadoc-plugin-1.7-SNAPSHOT\plugin.jelly Element... javadoc:javadocwarnings Line...... 483 Column.... 11 String index out of range: -1 Total time: 13 seconds Finished at: Wed Sep 01 17:42:13 BRT 2004 I will see if I can narrow down the issue and realize what's going on. I guess the javadoc is generating some output in an unexpected format that crashes the parser (i.e, the JavadocWarningsTextToXml.java) - if that's the case, I think it would be safer to ignore such exceptions, at least while this new feature is not stable yet (as we might face some similar issues in the future as the users uses other JDKs or javadoclets to generate the output). --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
