You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Lester Ecarma (JIRA)" <ji...@codehaus.org> on 2005/10/11 07:33:11 UTC

[jira] Commented: (MNG-968) linkoffline tag is not parsed properly

    [ http://jira.codehaus.org/browse/MNG-968?page=comments#action_48290 ] 

Lester Ecarma commented on MNG-968:
-----------------------------------

The -linkoffline arguments should be comma separated (they always come in pairs, right?), but even with that declared correctly it's still throwing the same error described above. 

Another thing, it doesn't seem like javadoc:javadoc currently supports multiple -linkoffline options, or -link for that matter. How are multiple -link and -linkoffline configured in the pom? I saw a reference of an old implementation (I think) in http://maven.apache.org/reference/plugins/javadoc/faq.html#offlineLinks, although there seem to be some inconsistencies in the use of comma for single (used to separate for the argument pair) and multiple (used to separate multiple argument pairs, and uses # to separate each argument in a pair) linkoffline options.  Could anyone give some advice as to what the specs are for this so that I can try and take a stab at it?

Could this be related to MNG-1004?

Thanks.

> linkoffline tag is not parsed properly
> --------------------------------------
>
>          Key: MNG-968
>          URL: http://jira.codehaus.org/browse/MNG-968
>      Project: Maven 2
>         Type: Bug
>   Components: maven-javadoc-plugin
>     Versions: 2.0-beta-1
>     Reporter: David DIDIER
>      Fix For: 2.0-beta-4

>
>
> When using the javadoc plugin with linkoffline, my pom contains :
> <reporting>
>     <plugins>
>         <plugin>
>             <groupId>org.apache.maven.plugins</groupId>
>             <artifactId>maven-javadoc-plugin</artifactId>
>             <version>2.0-beta-1</version>
>             <configuration>
>                 <linkoffline>http://java.sun.com/j2se/1.4.2/docs/api/ path/to/package-list/</linkoffline>
>                 <source>1.4</source>
>             </configuration>
>         </plugin>
>         ...
>     </plugins>
> </reporting>
> but the generated command is then :
> javadoc.exe ... -linkoffline "http://java.sun.com/j2se/1.4.2/docs/api/ path/to/package-list/" ...
> according to the javadoc documentation, it seems that the syntax should be :
> javadoc.exe ... -linkoffline http://java.sun.com/j2se/1.4.2/docs/api/ path/to/package-list/  ... 
> (without ")
> Here is the interesting part of the trace :
> [INFO] [javadoc:javadoc]
> [INFO] C:\Programmation\j2sdk1.4.2_08\jre\..\bin\javadoc.exe -package-source 1.4 -sourcePath D:\projets\ndd\root\..\ndd14-base\src\main\java -classpath D:\projets\ndd\root\..\base\target\classes;d:\temp\maven2\repository\junit\junit\3.8.1\junit-3.8.1.jar;d:\temp\maven2\repository\log4j\log4j\1.2.9\log4j-1.2.9.jar;d:\temp\maven2\repository\commons-io\commons-io\1.0\commons-io-1.0.jar;d:\temp\maven2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\temp\maven2\repository\commons-primitives\commons-primitives\1.0\commons-primitives-1.0.jar -author -bottom "Copyright null DD. All Rights Reserved." -charset ISO-8859-1 -d D:\projets\ndd\root\..\base\target\javadoc\apidocs -doctitle "NDD Base project 0.20-SNAPSHOT API" -linkoffline "http://java.sun.com/j2se/1.4.2/docs/api/ ../root/src/javadoc/j2sdk-1.4.2/" -stylesheetfile D:\projets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css -use -version -windowtitle "NDD Base project 0.20-SNAPSHOT API" @files
> javadoc: Illegal package name: "D:\projets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css"

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org