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 2015/04/14 00:44:12 UTC
[jira] [Updated] (ACCUMULO-2863) Generate a VERSIONS file for
bundled dependencies
[ https://issues.apache.org/jira/browse/ACCUMULO-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Tubbs updated ACCUMULO-2863:
----------------------------------------
Fix Version/s: (was: 1.8.0)
1.7.0
Assignee: Christopher Tubbs
Summary: Generate a VERSIONS file for bundled dependencies (was: Generate a DEPENDENCIES listing file)
> Generate a VERSIONS file for bundled dependencies
> -------------------------------------------------
>
> Key: ACCUMULO-2863
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2863
> Project: Accumulo
> Issue Type: Improvement
> Components: build
> Reporter: Christopher Tubbs
> Assignee: Christopher Tubbs
> Labels: newbie
> Fix For: 1.7.0
>
>
> We strip versions off of dependencies we package in the lib directory of our tarball. This is done for a few beneficial reasons (primarily: avoid classpath polution with multiple versions of the same jar, and ease maintenance of scripts that configure the classpath).
> However, it would be convenient to convey information in the bin.tar.gz about which versions of those libraries are included, so they don't have to go spelunking into the jars' META-INF to peek at their POM, or back to SCM to view the dependencyManagement section.
> It looks like this might be relatively easy to do with an execution of maven-dependency-plugin's list goal, with includeScope set to runtime and outputFile set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)