Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <876380457.351981266473488067.JavaMail.jira@brutus.apache.org>
Date: Thu, 18 Feb 2010 06:11:28 +0000 (UTC)
From: "Scott Carey (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Updated: (AVRO-417)  ivy maven install should also install
 -javadoc.jar as well
In-Reply-To: <779410257.322421266362967948.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AVRO-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Carey updated AVRO-417:
-----------------------------

    Status: Patch Available  (was: Open)

>  ivy maven install should also install -javadoc.jar as well
> -----------------------------------------------------------
>
>                 Key: AVRO-417
>                 URL: https://issues.apache.org/jira/browse/AVRO-417
>             Project: Avro
>          Issue Type: Bug
>    Affects Versions: 1.2.0, 1.1.0, 1.0.0, 1.3.0
>            Reporter: Scott Carey
>             Fix For: 1.3.0
>
>         Attachments: AVRO-417.patch
>
>
> Like sources, javadoc should be generated and published via maven.
> This means that in IDE's like Eclipse use of the Avro APIs will have handy javadoc tooltips and auto-complete options will contain javadoc.   Also, it is becoming the standard way to distribute javadoc alongside code and source.
> I assume, this is done very similarly to AVRO-416.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.