> Sigh, for the n-th time. I did generate the javadocs with jdk5.
Oups! Sorry, I didn't realized that. Yes given your report, removing the profile
was probably the best action to do.
Martin
-
This SF.net email is spo
Martin Desruisseaux ha scritto:
> The same should apply to every class in the whole GeoTools API. This
> information
> has not been added because of a weid idea of mine - users really asked for
> that
> on the mailing list. They want to know in which JAR is a class. This
> information
> will not
The requirement for Java 5 in JavaDoc generation was because I wrote two taglets
http://svn.geotools.org/geotools/trunk/gt/build/maven/javadoc/src/main/java/org/geotools/maven/taglet/
and unfortunatly the taglet API was not stabilized before Java 5, so those
taglets will not work when generating
Adrian Custer ha scritto:
> Hey Andrea,
>
> Like so many things in Geotools, Martin is probably the only person who
> fully understands the reason for this maven block and who can tell us
> where to check in the javadocs to see if there are broken links or
> missing pieces when the javadocs are bu
Hey Andrea,
Like so many things in Geotools, Martin is probably the only person who
fully understands the reason for this maven block and who can tell us
where to check in the javadocs to see if there are broken links or
missing pieces when the javadocs are built with 1.4. And Martin is so
busy th
Andrea Aime ha scritto:
> Hi,
> the troubles with the javadoc generation (see users mailing list)
> were related to a profile we have in the main pom:
>
>
>java5
>
> 1.5
>
>
>
>
> org.apache.maven.plugins
>
Hi,
the troubles with the javadoc generation (see users mailing list)
were related to a profile we have in the main pom:
java5
1.5
org.apache.maven.plugins
maven-javadoc-plugin
