[
https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-2537:
-------------------------------------
I think the problem is that WildFly can only pull in:
{quote}
<dependency>
<groupId>org.jboss.narayana.jts</groupId>
<artifactId>narayana-jts-idlj</artifactId>
<version>${version.org.jboss.narayana}</version>
</dependency>
{quote}
https://github.com/wildfly/wildfly/blob/master/pom.xml#L4435
It may work now if one of your builds is building that idlj jar but it is still incorrect
as WFLY needs updating to build with narayana-jts-ibmorb artifact (and may even need a
subsystem change).
I think for now we should try to avoid the need to build the app server in our job and
wait until WFLY can use the IBM ORB - what do you think?
Need to provide a WFLY option to build with IBM orb instead of
OpenJDK for Narayana
-----------------------------------------------------------------------------------
Key: JBTM-2537
URL:
https://issues.jboss.org/browse/JBTM-2537
Project: JBoss Transaction Manager
Issue Type: Bug
Components: JTS
Reporter: Tom Jenkinson
Assignee: Michael Musgrove
Fix For: 5.next
I am not sure if this might really need a WFLY change instead of JBTM?
I guess it finally caught us after an .m2 wipe?
http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)