You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Andy Jefferson (JIRA)" <ji...@apache.org> on 2008/11/06 11:55:44 UTC

[jira] Created: (JDO-612) M2 pom is incorrect, result in problems with transitive dependencies

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


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.


[jira] Commented: (JDO-612) M2 pom is incorrect, result in problems with transitive dependencies

Posted by "Carlos Sanchez (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JDO-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647675#action_12647675 ] 

Carlos Sanchez commented on JDO-612:
------------------------------------

and to add scopes in a m1 pom so they are used when converted to m2 you can use

    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>3.8.1</version>
<properties>
<scope>test</scope>
</properties>
    </dependency>


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


[jira] Commented: (JDO-612) M2 pom is incorrect, result in problems with transitive dependencies

Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JDO-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647681#action_12647681 ] 

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

Hi Carlos,

Thanks for that. Should fix our problem.



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


[jira] Commented: (JDO-612) M2 pom is incorrect, result in problems with transitive dependencies

Posted by "Carlos Sanchez (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JDO-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647673#action_12647673 ] 

Carlos Sanchez commented on JDO-612:
------------------------------------

Michelle Caisse added the files to the apache Maven 1 repository, that is converted to Maven 2 and propagated to the central maven repository and mirrors

Unfortunately there's no easy way to fix it as it has been propagated to all mirrors, downstream users,... already. You could either do a new official release (2.2.1, 2.2.0.1, ...) or just copy the jar and the good pom as 2.2-1 (naming convention used before to fix bad poms with the same jar)

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


[jira] Updated: (JDO-612) M2 pom is incorrect, result in problems with transitive dependencies

Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JDO-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Russell updated JDO-612:
------------------------------

    Attachment: jdo-612.patch

Are there any other issues relating to the pom?

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


[jira] Commented: (JDO-612) M2 pom is incorrect, result in problems with transitive dependencies

Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Commented: (JDO-612) M2 pom is incorrect, result in problems with transitive dependencies

Posted by "Carlos Sanchez (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JDO-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647744#action_12647744 ] 

Carlos Sanchez commented on JDO-612:
------------------------------------

other thing that you can set is 

<properties>
<optional>true</optional>
</properties> 

to prevent a dependency to be transitively pushed to downstream users (probably ant, maybe geronimo)



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


[jira] Resolved: (JDO-612) M2 pom is incorrect, result in problems with transitive dependencies

Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JDO-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Jefferson resolved JDO-612.
--------------------------------

    Resolution: Fixed

Marking as fixed; all discussed changes were applied

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