Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <435779492.1212747165092.JavaMail.jira@brutus>
Date: Fri, 6 Jun 2008 03:12:45 -0700 (PDT)
From: "Xavier Hanin (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Resolved: (IVY-325) declare source and javadoc artifacts in
 maven2 modules
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Xavier Hanin resolved IVY-325.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-RC1

I've just implemented this, now m2 modules expose both a "sources" and "javadoc" configuration, containing the corresponding artifact if it exists.

I agree that this is not enough to work with sources and javadocs easily. Indeed, you can easily get sources and/or javadoc of one dependency, but it doesn't work transitively. To get sources and/or javadoc only of artifacts requested by the configurations actually needed, some kind of flag would be better.

> declare source and javadoc artifacts in maven2 modules
> ------------------------------------------------------
>
>                 Key: IVY-325
>                 URL: https://issues.apache.org/jira/browse/IVY-325
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Maven Compatibility
>    Affects Versions: 1.4
>            Reporter: Xavier Hanin
>            Assignee: Xavier Hanin
>             Fix For: 2.0-RC1
>
>
> Maven2 modules created when Ivy parses poms do not declare any source or javadoc artifact, while they sometimes offer one on ibiblio. Declaring such artifact could ease the integration of maven2 modules with source and javadoc attachments.

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