You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Frank Griffin (JIRA)" <ji...@codehaus.org> on 2010/08/02 19:32:32 UTC
[jira] Created: (MJAVADOC-287) -sourcepath with "." or ".." causes
"invalid package name" errors
-sourcepath with "." or ".." causes "invalid package name" errors
-----------------------------------------------------------------
Key: MJAVADOC-287
URL: http://jira.codehaus.org/browse/MJAVADOC-287
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.7
Environment: Mandriva Linux 2010.1
Reporter: Frank Griffin
If you create a dummy project to run a custom doclet against the source tree of a different project, and specify the -sourcepath as
<sourcepath>${basedir}/../otherproject/src/main/java</sourcepath>
execution will fail with:
An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - Illegal package name: "/data/ftg/dvd-ejbgen/../dvd/target/generated-sources/maven-plugin"
This happens because the argfile is built using the Absolute Path of -sourcepath rather than the Canonical Path, e.g.
'/data/ftg/dvd-ejbgen/../dvd/src/main/java/org/profsoftsvcs/dbutils/DVD/DBUtDVDEntityBean.java'
'/data/ftg/dvd-ejbgen/../dvd/src/main/java/org/profsoftsvcs/dbutils/DVD/DBUtDVDSessionBeanImpl.java'
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MJAVADOC-287) -sourcepath with "." or ".." causes
"invalid package name" errors
Posted by "Frank Griffin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Griffin closed MJAVADOC-287.
----------------------------------
Resolution: Not A Bug
My error here. The custom doclet was returning 1 rather than 2 from optionLength() for options that took an argument of a path, causing Javadoc to interpret the path as a packagename to be processed. After correcting that, the path resolution seems to occur as it should (although not in the part of the source I was looking at).
> -sourcepath with "." or ".." causes "invalid package name" errors
> -----------------------------------------------------------------
>
> Key: MJAVADOC-287
> URL: http://jira.codehaus.org/browse/MJAVADOC-287
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.7
> Environment: Mandriva Linux 2010.1
> Reporter: Frank Griffin
>
> If you create a dummy project to run a custom doclet against the source tree of a different project, and specify the -sourcepath as
> <sourcepath>${basedir}/../otherproject/src/main/java</sourcepath>
> execution will fail with:
> An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - Illegal package name: "/data/ftg/dvd-ejbgen/../dvd/target/generated-sources/maven-plugin"
> This happens because the argfile is built using the Absolute Path of -sourcepath rather than the Canonical Path, e.g.
> '/data/ftg/dvd-ejbgen/../dvd/src/main/java/org/profsoftsvcs/dbutils/DVD/DBUtDVDEntityBean.java'
> '/data/ftg/dvd-ejbgen/../dvd/src/main/java/org/profsoftsvcs/dbutils/DVD/DBUtDVDSessionBeanImpl.java'
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira