You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Benson Margulies (Created) (JIRA)" <ji...@apache.org> on 2012/03/19 17:42:39 UTC
[jira] [Created] (ACCUMULO-470) Clean up maven-jar-plugin
configuration
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
[jira] [Commented] (ACCUMULO-470) Clean up maven-jar-plugin
configuration
Posted by "Benson Margulies (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (ACCUMULO-470) Clean up maven-jar-plugin
configuration
Posted by "Eric Newton (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233004#comment-13233004 ]
Eric Newton commented on ACCUMULO-470:
--------------------------------------
<Sealed> was recommended to me as a security precaution. It is my understanding that it prevents someone from deploying a jar that would override the server classes, and perhaps allow someone to see data that they should not.
> 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
[jira] [Commented] (ACCUMULO-470) Clean up maven-jar-plugin
configuration
Posted by "Benson Margulies (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232722#comment-13232722 ]
Benson Margulies commented on ACCUMULO-470:
-------------------------------------------
Anyone know why <Sealed> is turned on?
> 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
[jira] [Commented] (ACCUMULO-470) Clean up maven-jar-plugin
configuration
Posted by "Benson Margulies (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232724#comment-13232724 ]
Benson Margulies commented on ACCUMULO-470:
-------------------------------------------
1302535 purports to take care of this.
> 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