[ 
https://issues.apache.org/jira/browse/JDO-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647735#action_12647735
 ] 

Craig Russell commented on JDO-612:
-----------------------------------

svn commit -m "JDO-612 Add test scope to junit and ant dependencies" 
api2-legacy/project.xml api2/project.xml 
Sending api2/project.xml 
Sending api2-legacy/project.xml 
Transmitting file data .. 
Committed revision 714158. 

These should fix the scope issues for the api2 projects. Awaiting other 
feedback before closing the issue.

> M2 pom is incorrect, result in problems with transitive dependencies
> --------------------------------------------------------------------
>
>                 Key: JDO-612
>                 URL: https://issues.apache.org/jira/browse/JDO-612
>             Project: JDO
>          Issue Type: Bug
>          Components: api2
>            Reporter: Andy Jefferson
>             Fix For: JDO 2 maintenance release 3
>
>         Attachments: jdo-612.patch
>
>
> jdo2-api.jar is in an M2 repository
> http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/jdo/jdo2-api/2.2/
> and the pom has
> <dependencies>
>     <dependency>
>       <groupId>javax.transaction</groupId>
>       <artifactId>transaction-api</artifactId>
>       <version>1.1</version>
>     </dependency>
>     <dependency>
>       <groupId>org.apache.ant</groupId>
>       <artifactId>ant</artifactId>
>       <version>1.7.0</version>
>     </dependency>
>     <dependency>
>       <groupId>junit</groupId>
>       <artifactId>junit</artifactId>
>       <version>3.8.1</version>
>     </dependency>
>     <dependency>
>       <groupId>org.apache.geronimo.specs</groupId>
>       <artifactId>geronimo-jpa_3.0_spec</artifactId>
>       <version>1.0</version>
>     </dependency>
>   </dependencies>
> which is incomplete. All of these dependencies should be scoped to compile 
> AFAICS. The "junit" dep should be <scope>test</scope> since it is only for 
> tests.
> Since jdo2-api.jar is not built using M2 and has no such M2 pom.xml where is 
> this POM coming from ? (some automated Maven process to convert M1 poms to M2 
> poms?)

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

Reply via email to