[infinispan-issues] [JBoss JIRA] (ISPN-1509) Using Infinispan dependency in Gradle doesn't retrieve artifacts

[Antony Blakey (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640696#comment-12640696 ] 

Antony Blakey commented on ISPN-1509:
-------------------------------------

Actually, that hibernate example shows that it doesn't really work. If I do this:

{code}
compile('org.infinispan:infinispan-core:5.1.0.BETA3') { 
    artifact { 
        name='infinispan-core'
        type='jar'
    }
}
{code}

then I get the jar, but if I do this:

{code}
compile 'org.hibernate:hibernate-infinispan:4.0.0.CR5'
{code}

i.e. transitively including infinispan, then I get the source for infinispan-core *but not the jar*! So that strategy doesn't work for transitive dependencies. I think that at the very least the infinispan pom should be structured such that the primary jar (as opposed to the test jar) is automatically provided when including it as either a bare (direct) dependency or as a transitive dependency.
                
> Using Infinispan dependency in Gradle doesn't retrieve artifacts
> ----------------------------------------------------------------
>
>                 Key: ISPN-1509
>                 URL: https://issues.jboss.org/browse/ISPN-1509
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Build process
>    Affects Versions: 5.0.0.FINAL, 5.0.1.FINAL, 5.1.0.BETA3
>         Environment: Gradle milestone-3, milestone-5
>            Reporter: Antony Blakey
>            Assignee: Manik Surtani
>
> Using the maven dependencies from Gradle doesn't pull any artifacts or sub-dependencies. It seems this is because Gradle.Ivy isn't picking up the ${packaging} variable inherited from the parent pom when resolving. If I replace all the ${packaging} references with 'jar' and rebuild Infinispan then it works, at least for infinispan-core - org.infinispan:infinispan still doesn't grab anything, not sure if it should though.
> Fixes appropriate for ivy/ant don't work for Gradle i.e. it doesn't pick up ivy config files.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira