[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=12640686#comment-12640686 ] 

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

Surely though, having to put that 'artifact' element in shouldn't be required. Why can't I just depend on infinispan-core like every other maven package. Do I have to do that for every infinispan component? I would have thought that the internal artifact structure is not part of the public face of a maven artifact. Do you regard it as being part of the contract for using infinispan?
                
> 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