[
https://issues.jboss.org/browse/JBTM-1196?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1196:
-------------------------------------
Sent the following email to jboss-as7-dev(a)lists.jboss.org (preferred location for dev
discussion by AS team).
{code}
Coping with cyclic test dependencies
------------------------------------
All,
JBoss transactions uses Arquillian for some of the project tests. Therefore JBossTS has a
dependency on AS7 (for the Arquillian container dependency), but as AS7 consumes JBossTS,
the target AS7 version is not available when we do the release of JBossTS. We get around
this at the moment by referencing a SNAPSHOT version of AS7 in the Arquillian container
dependency. However, this does mean that our release will reference the SNAPSHOT
dependency.
This must be a common issue that other projects have. I was wondering what the accepted
pattern was to solve this issue?
Paul.
{code}
Cyclic dependency between AS7 and (txframework and XTS)
-------------------------------------------------------
Key: JBTM-1196
URL:
https://issues.jboss.org/browse/JBTM-1196
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: TXFramework, XTS
Reporter: Tom Jenkinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
Pom uses jboss-as.version which assumes a build of AS7 but in theory that version would
not exist until this version of Narayana was released.
At the moment it works because we run against a SNAPSHOT version.
Just brainstorming, but can the tests be ran without AS7 or can XTS be hot deployed by
the tests or should these tests be ran in the AS7 test suite?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira