[
https://jira.jboss.org/jira/browse/JBTM-679?page=com.atlassian.jira.plugi...
]
Andrew Dinn commented on JBTM-679:
----------------------------------
Ok, checked in changes for almost all of the build scripts so they now refer to the parent
JBossTS directory for their external libraries bar junit. The only top level module not
yet changed is localjunit which needs commons-logging (that's already pulled in),
commons-httpclient and commons-codec.jar. Pulling in the correct junit jar will require
rejigging most of the XTS tests as JBossTS installs an incompatible version.
Enable use of maven to import external lib jars into XTS
--------------------------------------------------------
Key: JBTM-679
URL:
https://jira.jboss.org/jira/browse/JBTM-679
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.9.0
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.10.0
The XTS build process employs a variety of external jars:
JBossTS jars
JBossWS jars (including Java EE API jars, JBossWS native jars and CXF jars)
JBossAS jars (including Java EE API jars)
other java jars (junit)
The build process should normally employ the JBossTS jars produced by building JBossTS
in the source tree containing XTS as a subtree. However, in the case of the other sets of
jars it should be possible to build XTS with a guarantee that the build employs known
versions of each of the required jars.
This should be achieved using maven to resolve dependencies and download the required
jars. In the case of the AS and WS jars the versions should be derived from the
component-matrix pom associated with a specific version of the AS to which the XTS and TS
tree is matched.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira