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 be part of the javadoc if you create it with Java 4.
Sigh, for the n-th time. I did generate the javadocs with jdk5. I did
not say the taglet was a problem. All I said was that automated
activation of the following profile caused the problem:
<profile>
<id>java5</id>
<activation>
<jdk>1.5</jdk>
</activation>
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<source>1.5</source>
</configuration>
</plugin>
</plugins>
</reporting>
</profile>
Commenting out this profile from the pom allowed to have aggregate
javadocs properly generated using jdk5 (the profile would not
have been a problem if I wasn't using jdk4 since it would not
have activated at all).
I think this one is somehow interfering with the javadoc plugin
configuration, but how, I don't know (to my knowledge it should
only have added the <source>1.5<source> on top of the base configuration
specified in the <build> section, but that's not what is happening).
Anyways, I don't know if it's worth investigating more.
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
