accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1436) Dependencies on sibling modules in Accumulo shouldn't be in the "provided" scope
Date Tue, 21 May 2013 00:57:16 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662529#comment-13662529
] 

Hudson commented on ACCUMULO-1436:
----------------------------------

Integrated in Accumulo-1.5-Hadoop-2.0 #130 (See [https://builds.apache.org/job/Accumulo-1.5-Hadoop-2.0/130/])
    ACCUMULO-1436 dependency cleanup to make accumulo artifacts non-provided (Revision 1484616)

     Result = SUCCESS
ctubbsii : 
Files : 
* /accumulo/branches/1.5/core/pom.xml
* /accumulo/branches/1.5/examples/simple/pom.xml
* /accumulo/branches/1.5/proxy/pom.xml
* /accumulo/branches/1.5/server/pom.xml
* /accumulo/branches/1.5/start/pom.xml
* /accumulo/branches/1.5/test/pom.xml

                
> Dependencies on sibling modules in Accumulo shouldn't be in the "provided" scope
> --------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-1436
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1436
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.5.1
>
>
> Marking dependencies as "provided" for artifacts we're generating, is confusing, as it
requires end-users to add additional dependencies that aren't necessarily intuitive (such
as the accumulo-start jar, to get MiniAccumuloCluster to work when depending on accumulo-server).

--
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

Mime
View raw message