You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2013/05/05 23:06:17 UTC

[jira] [Updated] (ACCUMULO-470) Clean up maven-jar-plugin configuration

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

Christopher Tubbs updated ACCUMULO-470:
---------------------------------------

    Fix Version/s: 1.5.0
         Assignee: Christopher Tubbs  (was: Benson Margulies)
    
> Clean up maven-jar-plugin configuration
> ---------------------------------------
>
>                 Key: ACCUMULO-470
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-470
>             Project: Accumulo
>          Issue Type: Task
>          Components: dist
>            Reporter: Benson Margulies
>            Assignee: Christopher Tubbs
>             Fix For: 1.5.0
>
>
> The top-level pom has a configuration for the maven-jar-plugin that sets a relative pathname for the output, and a miscellaneous collection of <include>s. THis results in jars ending up in some odd lib directories down the build. The <include> elements don't make much sense at all.
> Reduce the top-level pom to specifying only really global config (the manifest stuff), and push the lib dir into the specific poms that contribute to the top-level lib dir. Also remove the includes and just let the default pick up everything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira