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

[Galder Zamarreño (Commented) (JIRA)]

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

Galder Zamarreño commented on ISPN-1509:
----------------------------------------

The reason for introducing ${packaging} was to be able to speed up builds by selectively deciding when to build OSGI bundles on top of jars. So, when you wanted to build quickly, you'd disable the 'extras' profile that used 'bundle' packaging and instead you'd use 'jar' packaging. Seems like the resulting pom.xml files can be annoying for some people, so I don't have any major issues going back to the old format at least for OSGI bundles. 'extras' profile will remain there for enforcer checks and source jar generation. 
                
> 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