Return-Path: 
 <dev-return-4159-apmail-accumulo-dev-archive=accumulo.apache.org@accumulo.apache.org>
X-Original-To: apmail-accumulo-dev-archive@www.apache.org
Delivered-To: apmail-accumulo-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6FD20D8A4
	for <apmail-accumulo-dev-archive@www.apache.org>;
 Wed,  1 Aug 2012 23:29:38 +0000 (UTC)
Received: (qmail 54920 invoked by uid 500); 1 Aug 2012 23:29:38 -0000
Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org
Received: (qmail 54884 invoked by uid 500); 1 Aug 2012 23:29:38 -0000
Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@accumulo.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@accumulo.apache.org>
List-Post: <mailto:dev@accumulo.apache.org>
List-Id: <dev.accumulo.apache.org>
Reply-To: dev@accumulo.apache.org
Delivered-To: mailing list dev@accumulo.apache.org
Received: (qmail 54876 invoked by uid 99); 1 Aug 2012 23:29:38 -0000
Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2012 23:29:38 +0000
Received: from localhost (HELO mail-vc0-f169.google.com) (127.0.0.1)
  (smtp-auth username vines, mechanism plain)
  by minotaur.apache.org (qpsmtpd/0.29) with ESMTP;
 Wed, 01 Aug 2012 23:29:37 +0000
Received: by vcbfl10 with SMTP id fl10so8643694vcb.0
        for <dev@accumulo.apache.org>; Wed, 01 Aug 2012 16:29:36 -0700 (PDT)
Received: by 10.52.95.225 with SMTP id dn1mr16028866vdb.99.1343863776621; Wed,
 01 Aug 2012 16:29:36 -0700 (PDT)
MIME-Version: 1.0
Reply-To: vines@apache.org
Received: by 10.220.200.76 with HTTP; Wed, 1 Aug 2012 16:29:16 -0700 (PDT)
In-Reply-To: 
 <CAOiJXP5Xcyy1xSpbmMRyH9pOzHyeF7d2J=sgQENsyZwvy3H76w@mail.gmail.com>
References: 
 <CAOiJXP5Xcyy1xSpbmMRyH9pOzHyeF7d2J=sgQENsyZwvy3H76w@mail.gmail.com>
From: John Vines <vines@apache.org>
Date: Wed, 1 Aug 2012 19:29:16 -0400
Message-ID: 
 <CADczPYTTNF93vsQT4weSfqJ4rhn4E0hisjieVb1Kf3FNZr2fwA@mail.gmail.com>
Subject: Re: Why Specify Javadoc Version?
To: dev@accumulo.apache.org
Content-Type: multipart/alternative; boundary=20cf307f34d008351204c63cab71

--20cf307f34d008351204c63cab71
Content-Type: text/plain; charset=ISO-8859-1

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

--20cf307f34d008351204c63cab71--