[
https://issues.apache.org/jira/browse/ACCUMULO-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233368#comment-13233368
]
Benson Margulies commented on ACCUMULO-470:
-------------------------------------------
So, what you'd doing is preventing jars in 'ext' from defining classes in the
core packages. OK, I get it.
> 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
> Affects Versions: 1.5.0-SNAPSHOT
> Reporter: Benson Margulies
> Assignee: Benson Margulies
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
