You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Thorsten Heit <th...@gmx.de> on 2007/02/26 12:09:26 UTC
[m2.0.5] Javadoc generation for older code
Hi,
we're developing using JDK 1.4, and unfortunately someone uses "enum" as a variable name somewhere in one of his source files. Since "enum" is a reserved keyword for Java 5 and higher, executing javadoc results in a couple of errors:
(...)
Loading source files for package ukv.lrkern...
d:\workspaces\sukv-maven\CAccess\src\ukv\lrkern\LRKern.java:10948: as of release 5, 'enum' is a keyword, and may not be used as an identifier
(use -source 1.4 or lower to use 'enum' as an identifier)
Enumeration enum = map.keys();
etc.
In the reportings section in my pom.xml I added
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.2</version>
<configuration>
<source>1.4</source>
</configuration>
</plugin>
but that didn't help. When I execute Javadoc in the command line using the "-source 1.4" parameter, the errors remain (although the program tells me to add this parameter...).
Until the corresponding classes are updated or refactored, how can I let Javadoc generate the API documentation?
Regards
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2.0.5] Javadoc generation for older code
Posted by Thorsten Heit <th...@gmx.de>.
Hi Vincent,
> > Isn't there a trick to force the Javadoc command to ignore JDK >= 1.5
> keywords?
>
> No AFAIK
Ok, thanks. Bad, though...
Cheers
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2.0.5] Javadoc generation for older code
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Thorsten,
2007/2/26, Thorsten Heit <th...@gmx.de>:
> Hi Vincent,
>
>
> > > Until the corresponding classes are updated or refactored, how can I let
> > Javadoc generate the API documentation?
> >
> > Add -Ddebug=true
> > http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html#How%20to%20know%20exactly%20the%20Javadoc%20command%20line
>
> The parameters listed there are basically the same that I already tried on the command line but that also doesn't work:
>
> %> javadoc -source 1.4 -sourcepath src/ -d target/site/apidocs/ <package list>
>
> Loading source files for package ukv.lrkern...
> d:\workspaces\sukv-maven\CAccess\src\ukv\lrkern\LRKern.java:10948: as of release 5, 'enum' is a keyword, and may not be used as an identifier
> (use -source 1.4 or lower to use 'enum' as an identifier)
> Enumeration enum = map.keys();
> ^
> etc.
>
> Isn't there a trick to force the Javadoc command to ignore JDK >= 1.5 keywords?
No AFAIK
>
>
> Regards
>
> Thorsten
>
>
> PS: I'm using JDK 6 as default JDK on my machine (Windows XP).
Sounds like http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6507179
Cheers,
Vincent
>
> ---------------------------------------------------------------------
> 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: [m2.0.5] Javadoc generation for older code
Posted by Thorsten Heit <th...@gmx.de>.
Hi Vincent,
> > Until the corresponding classes are updated or refactored, how can I let
> Javadoc generate the API documentation?
>
> Add -Ddebug=true
> http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html#How%20to%20know%20exactly%20the%20Javadoc%20command%20line
The parameters listed there are basically the same that I already tried on the command line but that also doesn't work:
%> javadoc -source 1.4 -sourcepath src/ -d target/site/apidocs/ <package list>
Loading source files for package ukv.lrkern...
d:\workspaces\sukv-maven\CAccess\src\ukv\lrkern\LRKern.java:10948: as of release 5, 'enum' is a keyword, and may not be used as an identifier
(use -source 1.4 or lower to use 'enum' as an identifier)
Enumeration enum = map.keys();
^
etc.
Isn't there a trick to force the Javadoc command to ignore JDK >= 1.5 keywords?
Regards
Thorsten
PS: I'm using JDK 6 as default JDK on my machine (Windows XP).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
How to generate a report
Posted by Niels Gylling <ng...@it-practice.dk>.
Can anyone provide a working example of a hello-world report that uses a
Sink to generate a simple html report?
I have seen various examples of current reports that generate the report
differently. It seems that eg. the SiteRenderer has changed location
recently, and my report is not generated at all even if a link to is has
been produced..
I tried to create a mojo that implements MavenReport or a plugin class
that extend AbstractMavenReport with no luck.
/Niels
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2.0.5] Javadoc generation for older code
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Thorsten,
2007/2/26, Thorsten Heit <th...@gmx.de>:
> Hi,
>
> we're developing using JDK 1.4, and unfortunately someone uses "enum" as a variable name somewhere in one of his source files. Since "enum" is a reserved keyword for Java 5 and higher, executing javadoc results in a couple of errors:
>
> (...)
> Loading source files for package ukv.lrkern...
> d:\workspaces\sukv-maven\CAccess\src\ukv\lrkern\LRKern.java:10948: as of release 5, 'enum' is a keyword, and may not be used as an identifier
> (use -source 1.4 or lower to use 'enum' as an identifier)
> Enumeration enum = map.keys();
>
> etc.
>
> In the reportings section in my pom.xml I added
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-javadoc-plugin</artifactId>
> <version>2.2</version>
> <configuration>
> <source>1.4</source>
> </configuration>
> </plugin>
>
> but that didn't help. When I execute Javadoc in the command line using the "-source 1.4" parameter, the errors remain (although the program tells me to add this parameter...).
>
> Until the corresponding classes are updated or refactored, how can I let Javadoc generate the API documentation?
Add -Ddebug=true
http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html#How%20to%20know%20exactly%20the%20Javadoc%20command%20line
Cheers,
Vincent
>
>
> Regards
>
> Thorsten
>
> ---------------------------------------------------------------------
> 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