[jbossts-issues] [JBoss JIRA] (JBTM-1800) Improve XTS recovery tests to not use a checked-in byteman.jar

Amos Feng (JIRA) jira-events at lists.jboss.org
Tue Jul 16 22:40:58 EDT 2013


    [ https://issues.jboss.org/browse/JBTM-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790163#comment-12790163 ] 

Amos Feng commented on JBTM-1800:
---------------------------------

[~mmusgrov] no problem. I've update the commit and re-test on CI
                
> Improve XTS recovery tests to not use a checked-in byteman.jar
> --------------------------------------------------------------
>
>                 Key: JBTM-1800
>                 URL: https://issues.jboss.org/browse/JBTM-1800
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: XTS
>            Reporter: Paul Robinson
>            Assignee: Amos Feng
>             Fix For: 5.0.0.M4
>
>
> Notice the checked in version here: /XTS/localjunit/crash-recovery-tests/src/test/resources/lib/byteman.jar
> This is problematic as it falls outside of our dependency management done via maven. This could also be the cause of our intermittent Byteman issues as the jar could be very old.
> We need to understand why this is needed and find an alternative that uses the byteman dependency specified in the maven dependencies. Shinkwrap resolvers may be an option. Or we could use a maven plugin to get the jar at build time, based on the version specified in the maven dependencies. We do the latter here: https://github.com/jbosstm/jboss-as/blob/5_BRANCH/testsuite/integration/xts/pom.xml#L73

--
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


More information about the jbossts-issues mailing list