[ https://issues.apache.org/jira/browse/JDO-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-644: --------------------------------- Attachment: jta-01.patch The attached patch contains this change for all version 2 components. > Change JTA 1.1 dependency artifact id from "transaction-api" to "jta" > --------------------------------------------------------------------- > > Key: JDO-644 > URL: https://issues.apache.org/jira/browse/JDO-644 > Project: JDO > Issue Type: Improvement > Components: api2, api2-legacy, core2, enhancer2, fostore2, model2, > query2, runtime2, tck2, tck2-legacy, util2 > Affects Versions: JDO 2 maintenance release 3 > Reporter: Matthew T. Adams > Attachments: jta-01.patch > > > It appears that the Maven 2 artifact id for JTA 1.1 is "jta", not > "transaction-api". The Maven 2 POM is here: > http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/transaction/jta/1.1/jta-1.1.pom > For Maven1, the Maven 1 artifact id is "transaction-api": > http://download.java.net/maven/1/javax.transaction/poms/transaction-api-1.1.pom > Since most users use Maven2, this should be updated to "jta" and we, the team > producing JDO, should just manually install JTA 1.1 into our own local Maven > 1 repository with the artifact id "jta", using the Maven 2. Without this, it > is extremely annoying for users to have to work around this. > An alternative solution would be to upload to the Maven 1 central repo a copy > of JTA 1.1 with artifact id "jta", but I don't how to do that. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.