[jira] [Resolved] (EASYANT-12) plugins do not specify conf for ea:registerartifact calls

["Jean-Louis Boudart (JIRA)" <ji...@apache.org>]

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

Jean-Louis Boudart resolved EASYANT-12.
---------------------------------------

    Resolution: Fixed

Done on trunk
                
> plugins do not specify conf for ea:registerartifact calls
> ---------------------------------------------------------
>
>                 Key: EASYANT-12
>                 URL: https://issues.apache.org/jira/browse/EASYANT-12
>             Project: EasyAnt
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jean-Louis Boudart
>            Assignee: Jean-Louis Boudart
>             Fix For: 0.9
>
>
> this is a problem affecting javadoc, source-jar, package-test-jar, and package-war. if you use any of these plugins, an artifact publication is automatically added to all of your ivy configurations, and there is no way to override this behavior.
> Say you are building a war, "webapp.war", that depends on a core API module, "core.jar". If core.jar publishes a source jar, a test jar, and a javadoc zip, then all of those artifacts will be downloaded by the "webapp.war" build and put in WEB-INF/lib. This is probably not what you want.
> Each of these plugins should provide a property to control the ivy conf for the publication. We should probably also consider different default values for each of these plugins, because "*" or "default" will almost never be the right value. E.g most projects will want to publish the test jar in a conf named "test".
> I'd like to propose the following behavior:
>     * source-jar publishes to the "source" conf by default, override with "src.publish.conf"
>     * javadoc publishes to the "documentation" conf by default, override with "javadoc.publish.conf"
>     * package-test-jar publishes to the "${test.confs}" by default, override with "test.publish.conf"
>     * package-war publishes to the "${main.confs}" by default, override with "war.publish.conf"
> If any of the default configurations aren't defined, we fall back on "*".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira