[jbossts-issues] [JBoss JIRA] (JBTM-1694) upload orson and emma to repository.jboss.org
[
https://issues.jboss.org/browse/JBTM-1694?page=com.atlassian.jira.plugin....
]
Paul Gier commented on JBTM-1694:
---------------------------------
{quote} we are using a custom fork but only for community testing {quote}
That's what our thirdparty-releases repository [1] is for, so ideally we should upload
the patched release there. Were the patches also submitted to upstream emma so they can
get into a future release?
Moving the emma tests to a profile would be good.
[1]https://community.jboss.org/wiki/MavenDeployingaThirdpartyRelease
upload orson and emma to repository.jboss.org
---------------------------------------------
Key: JBTM-1694
URL: https://issues.jboss.org/browse/JBTM-1694
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Weinan Li
Assignee: Tom Jenkinson
Fix For: 4.17.5, 5.0.0.M3
Currently in ArjunaCore/arjuna/pom.xml:
{code}
<systemPath>${orson.jar.location}/../qa/dbdrivers/jConnect-6_0/classes/jconn3.jar</systemPath>
{code}
And user need to download orson.jar from internet and set orson jar location manually. Is
it okay that we upload the jars to repository.jboss.org?
--
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