[
https://issues.jboss.org/browse/ISPN-1211?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1211:
----------------------------------------
So, here's the dependency graph:
{code}core
|--> jbossjta-4.15.0.Final
|--> jbossws-common-2.0.0.Alpha3
|--> jbossws-spi-2.0.0.Alpha2
|--> jbossws-api-1.0.0-SNAPSHOT
{code}
I highly doubt we're using the JBoss WS module in JBoss TS at runtime. If anything
this snapshot could cause us trouble at build time if nexus is not available but that can
be controlled by the local update policy setting for snapshots.
So, I'm rejecting this.
Avoid master relying on a JBoss-WS snapshot
-------------------------------------------
Key: ISPN-1211
URL:
https://issues.jboss.org/browse/ISPN-1211
Project: Infinispan
Issue Type: Task
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Why is master relying on a JBoss-WS snapshot?
[INFO] ------------------------------------------------------------------------
[INFO] Building Infinispan Core 5.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/ws/jbos...
Investigate...
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira