[jbossts-issues] [JBoss JIRA] (JBTM-1694) Use emma jar from a Maven repo instead of checking into the build

Paul Gier (JIRA) jira-events at lists.jboss.org
Thu May 23 11:07:08 EDT 2013


     [ https://issues.jboss.org/browse/JBTM-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier updated JBTM-1694:
----------------------------

        Summary: Use emma jar from a Maven repo instead of checking into the build  (was: upload orson and emma to repository.jboss.org)
    Description: 
Currently in /pom.xml:

{code}
<systemPath>${emma.jar.location}</systemPath>
{code}


  was:
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?



Changed issue title and description to focus on emma, since there is another issue (JBTM-1671) for orson.
                
> Use emma jar from a Maven repo instead of checking into the build
> -----------------------------------------------------------------
>
>                 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 /pom.xml:
> {code}
> <systemPath>${emma.jar.location}</systemPath>
> {code}

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