db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew T. Adams (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JDO-416) jdo2-api Maven2 POM is incorrect
Date Fri, 18 May 2007 17:24:17 GMT

     [ https://issues.apache.org/jira/browse/JDO-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Matthew T. Adams resolved JDO-416.

    Resolution: Fixed

> jdo2-api Maven2 POM is incorrect
> --------------------------------
>                 Key: JDO-416
>                 URL: https://issues.apache.org/jira/browse/JDO-416
>             Project: JDO
>          Issue Type: Bug
>          Components: api2
>    Affects Versions: JDO 2 final
>            Reporter: Matthew T. Adams
>         Assigned To: Matthew T. Adams
>            Priority: Minor
>             Fix For: JDO 2 maintenance release 1
>         Attachments: jdo2-api-2.0.pom, jdo2-api-2.0.pom.md5, jdo2-api-2.0.pom.sha1
> The Maven2 central repo POM for artifact jdo2-api appears to be incorrect, and was apparently
generated by the Apache infrastructure team.  It needs to be corrected so that Maven2 users
that also use the JDO 2.0 API can use the central maven repo to retrieve JDO & its dependencies.
> The jdo2-api artifact has a dependency on JTA (specifically, on javax.transaction.Synchronization).
 It would be ideal for JTA to upload to the Maven2 repo a jar that the jdo2-api POM can reference,
but it is unknown if or when that will happen -- perhaps as part of Glassfish's release of
JTA 1.1.  Another complicating factor is which versions of the JDK that JTA 1.0.1, 1.0.1B,
1.1, or other versions will support.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message