8:02 p.m.
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.1.0.BETA3, 5.0.1.FINAL, 5.0.0.FINAL
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
3:23 a.m.
[
https://issues.jboss.org/browse/ISPN-1509?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1509:
----------------------------------------
Hmm, Hibernate uses Gradle and we have no problems linking Infinispan there. See:
https://github.com/hibernate/hibernate-core/blob/master/hibernate-infinis...
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
4:43 a.m.
[
https://issues.jboss.org/browse/ISPN-1509?page=com.atlassian.jira.plugin....
]
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
5:49 a.m.
[
https://issues.jboss.org/browse/ISPN-1509?page=com.atlassian.jira.plugin....
]
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
5:51 a.m.
[
https://issues.jboss.org/browse/ISPN-1509?page=com.atlassian.jira.plugin....
]
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
5:53 a.m.
New subject: [JBoss JIRA] (ISPN-1509) Restore original pom packaging settings to help Gradle builds
[
https://issues.jboss.org/browse/ISPN-1509?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1509:
-----------------------------------
Summary: Restore original pom packaging settings to help Gradle builds (was:
Using Infinispan dependency in Gradle doesn't retrieve artifacts)
Forum Reference: http://community.jboss.org/message/632566,
http://community.jboss.org/thread/165857 (was: http://community.jboss.org/message/632566,
http://community.jboss.org/thread/165857)
Restore original pom packaging settings to help Gradle builds
-------------------------------------------------------------
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
5:55 a.m.
New subject: [JBoss JIRA] (ISPN-1509) Restore original pom packaging settings to help Gradle builds
[
https://issues.jboss.org/browse/ISPN-1509?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1509:
-----------------------------------
Assignee: Galder Zamarreño (was: Manik Surtani)
Fix Version/s: 5.1.0.BETA4
5.1.0.FINAL
Forum Reference: http://community.jboss.org/message/632566,
http://community.jboss.org/thread/165857 (was: http://community.jboss.org/message/632566,
http://community.jboss.org/thread/165857)
Restore original pom packaging settings to help Gradle builds
-------------------------------------------------------------
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: Galder Zamarreño
Fix For: 5.1.0.BETA4, 5.1.0.FINAL
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
6 a.m.
New subject: [JBoss JIRA] (ISPN-1509) Restore original pom packaging settings to help Gradle builds
[
https://issues.jboss.org/browse/ISPN-1509?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1509:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/619
Restore original pom packaging settings to help Gradle builds
-------------------------------------------------------------
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: Galder Zamarreño
Fix For: 5.1.0.BETA4, 5.1.0.FINAL
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
6:10 a.m.
New subject: [JBoss JIRA] (ISPN-1509) Restore original pom packaging settings to help Gradle builds
[
https://issues.jboss.org/browse/ISPN-1509?page=com.atlassian.jira.plugin....
]
Antony Blakey commented on ISPN-1509:
-------------------------------------
Thanks!
Restore original pom packaging settings to help Gradle builds
-------------------------------------------------------------
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: Galder Zamarreño
Fix For: 5.1.0.BETA4, 5.1.0.FINAL
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
6:32 a.m.
New subject: [JBoss JIRA] (ISPN-1509) Restore original pom packaging settings to help Gradle builds
[
https://issues.jboss.org/browse/ISPN-1509?page=com.atlassian.jira.plugin....
]
Sanne Grinovero updated ISPN-1509:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Restore original pom packaging settings to help Gradle builds
-------------------------------------------------------------
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: Galder Zamarreño
Fix For: 5.1.0.BETA4, 5.1.0.FINAL
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
9:04 a.m.
New subject: [JBoss JIRA] (ISPN-1509) Restore original pom packaging settings to help Gradle builds
[
https://issues.jboss.org/browse/ISPN-1509?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1509:
----------------------------------------
This is integrated now, so checkout latest master, build it and see if it works fine for
you. I tested with Hibernate and it worked fine.
Restore original pom packaging settings to help Gradle builds
-------------------------------------------------------------
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: Galder Zamarreño
Fix For: 5.1.0.BETA4, 5.1.0.FINAL
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
6:58 p.m.
New subject: [JBoss JIRA] (ISPN-1509) Restore original pom packaging settings to help Gradle builds
[
https://issues.jboss.org/browse/ISPN-1509?page=com.atlassian.jira.plugin....
]
Antony Blakey commented on ISPN-1509:
-------------------------------------
Thanks Galder, that works fine for me.
Restore original pom packaging settings to help Gradle builds
-------------------------------------------------------------
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: Galder Zamarreño
Fix For: 5.1.0.BETA4, 5.1.0.FINAL
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
4822
days inactive
4823
days old
infinispan-issues@lists.jboss.org
11 comments
5 participants
participants (5)
-
Antony Blakey (Commented) (JIRA) -
Antony Blakey (Created) (JIRA)
-
Galder Zamarreño (Commented) (JIRA)
-
Galder Zamarreño (Updated) (JIRA)
-
Sanne Grinovero (Updated) (JIRA)