accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Wall (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ACCUMULO-1876) Problem using accumulo artifacts from ivy
Date Mon, 11 Nov 2013 01:34:17 GMT
Michael Wall created ACCUMULO-1876:
--------------------------------------

             Summary: Problem using accumulo artifacts from ivy
                 Key: ACCUMULO-1876
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1876
             Project: Accumulo
          Issue Type: Bug
          Components: master
    Affects Versions: 1.5.0, 1.5.1, 1.6.0, 1.6.1, 1.7.0
            Reporter: Michael Wall
            Priority: Minor


Defining an accumulo dependency in an ivy.xml file for any Accyumulo version greater than
1.4.4 results in the following error 

{noformat}
[ivy:resolve] 		::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve] 		::          UNRESOLVED DEPENDENCIES         ::
[ivy:resolve] 		::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve] 		:: org.slf4j#slf4j-api;${slf4j.version}: not found
[ivy:resolve] 		::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve] 

{noformat}

The issue appears to be that in the parent pom.xml, slf4j.version is only defined in profiles.
 Ivy doesn't load profiles when pulling from a maven repo, so the ${slf4j.version} is never
set.

One possible fix is to define a property earlier with the version, and allow the profiles
to overwrite.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message