[
https://issues.jboss.org/browse/JBTM-1802?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1802:
-------------------------------------
It does seem to make sense to me, the modules that use arquillian are:
./blacktie/blacktie-admin-services/pom.xml
./txbridge/pom.xml
./rest-tx/webservice/pom.xml
./rest-tx/integration/pom.xml
./ArjunaJTA/cdi/pom.xml
./txframework/pom.xml
./XTS/localjunit/pom.xml
./XTS/localjunit/unit/pom.xml
For now the BlackTie pom is isolated (i.e. does not inherit from the root pom.xml)
therefore it seems that someone familiar with TXB, XTS, txf, CDI and RTS would be best
placed to perform this work.
Consider moving Arquillian profiles to root pom.xml
---------------------------------------------------
Key: JBTM-1802
URL:
https://issues.jboss.org/browse/JBTM-1802
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Build System
Reporter: Paul Robinson
Assignee: Tom Jenkinson
Priority: Minor
Fix For: 5.0.0.M4
We have three Arquillian profiles (for managed, remote and ipv6-managed) present in the
pom of nearly every test that uses Arquillian. I suspect they can all be identical and
thus placed int he root pom.xml. This should simplify maintenance and will ensure any
fixes to this config are made throughout.
The problem is that we may have legitimate reasons for this config to differ for some
tests. Maybe we could use overrides in these cases.
Assigning to Tom for his input.
--
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