accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Vines <vi...@apache.org>
Subject Re: Why Specify Javadoc Version?
Date Wed, 01 Aug 2012 23:29:16 GMT
Because our target JDK version is 1.6. While Java aims to be fully backward
compatible, there is the chance that the behavior of something changes with
ill consequences. Our target java version is 1.6, so our javadoc version is
1.6 to match.

John

On Wed, Aug 1, 2012 at 6:53 PM, David Medinets <david.medinets@gmail.com>wrote:

> In pom.xml and examples/wikisearch/pom.xml, I see that javadoc v1.6 is
> specified.
>
>      <plugin>
>         <artifactId>maven-javadoc-plugin</artifactId>
>         <configuration>
>           <encoding>UTF-8</encoding>
>           <quiet>true</quiet>
>           <jarOutputDirectory>lib</jarOutputDirectory>
>           <reportOutputDirectory>docs</reportOutputDirectory>
>           <javadocVersion>1.6</javadocVersion>
>           <additionalJOption>-J-Xmx512m</additionalJOption>
>         </configuration>
>       </plugin>
>
> I am using Java v1.7. When I try to build the javadocs, this version
> specificity generates a warning.  However, if I remove the
> javadocVersion tag then the javadocs seem to generate fine. You can
> check 'em out at http://affy.com/javadoc/accumulo/1_5_0_SNAPSHOT.
>
> Is there any objection to my removing the javadocVersion tag?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message