You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carsten Ziegeler (JIRA)" <ji...@codehaus.org> on 2007/01/16 11:19:40 UTC
[jira] Created: (MEV-490) Invalid or problematic Spring POMS
Invalid or problematic Spring POMS
----------------------------------
Key: MEV-490
URL: http://jira.codehaus.org/browse/MEV-490
Project: Maven Evangelism
Issue Type: Bug
Components: Invalid POM
Reporter: Carsten Ziegeler
The Spring poms, for example spring-beans, version 2.0.2 use the following dependencies:
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>spring-core</artifactId>
<version>${project.version}</version>
</dependency>
Which means, they are using variables in the poms. In some cases, these variables are resolved correctly, but in some cases however they are not, causing problems.
Imho, it would be better to resolve variables for released poms to avoid any problems (or if variables are allowed, this is a maven bug then)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEV-490) Invalid or problematic Spring POMS
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-490?page=comments#action_85179 ]
Carlos Sanchez commented on MEV-490:
------------------------------------
in what cases are not resolved correctly? it shouldn't be a problem
> Invalid or problematic Spring POMS
> ----------------------------------
>
> Key: MEV-490
> URL: http://jira.codehaus.org/browse/MEV-490
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid POM
> Reporter: Carsten Ziegeler
>
> The Spring poms, for example spring-beans, version 2.0.2 use the following dependencies:
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>spring-core</artifactId>
> <version>${project.version}</version>
> </dependency>
> Which means, they are using variables in the poms. In some cases, these variables are resolved correctly, but in some cases however they are not, causing problems.
> Imho, it would be better to resolve variables for released poms to avoid any problems (or if variables are allowed, this is a maven bug then)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2782) Version property in dependencies is not
expanded correctly
Posted by "Kenney Westerhof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenney Westerhof closed MNG-2782.
---------------------------------
Resolution: Duplicate
> Version property in dependencies is not expanded correctly
> ----------------------------------------------------------
>
> Key: MNG-2782
> URL: http://jira.codehaus.org/browse/MNG-2782
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Reporter: Carsten Ziegeler
> Fix For: Reviewed Pending Version Assignment
>
>
> The Spring poms, for example spring-beans, version 2.0.2 use the following dependencies:
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>spring-core</artifactId>
> <version>${project.version}</version>
> </dependency>
> Which means, they are using variables in the poms. In some cases, these variables are resolved correctly, but in some cases however they are not, causing problems.
> Imho, it would be better to resolve variables for released poms to avoid any problems (or if variables are allowed, this is a maven bug then)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MNG-2782) Invalid or problematic Spring POMS
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2782?page=all ]
Carlos Sanchez moved MEV-490 to MNG-2782:
-----------------------------------------
Priority: Major
Group ID: (was: org.springframework)
Version: (was: 2.0.x)
Component/s: (was: Invalid POM)
Dependencies
Complexity: Intermediate
Workflow: Maven New (was: jira)
Key: MNG-2782 (was: MEV-490)
Project: Maven 2 (was: Maven Evangelism)
> Invalid or problematic Spring POMS
> ----------------------------------
>
> Key: MNG-2782
> URL: http://jira.codehaus.org/browse/MNG-2782
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Reporter: Carsten Ziegeler
>
> The Spring poms, for example spring-beans, version 2.0.2 use the following dependencies:
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>spring-core</artifactId>
> <version>${project.version}</version>
> </dependency>
> Which means, they are using variables in the poms. In some cases, these variables are resolved correctly, but in some cases however they are not, causing problems.
> Imho, it would be better to resolve variables for released poms to avoid any problems (or if variables are allowed, this is a maven bug then)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEV-490) Invalid or problematic Spring POMS
Posted by "Carsten Ziegeler (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-490?page=comments#action_85224 ]
Carsten Ziegeler commented on MEV-490:
--------------------------------------
Yes, this works in standard scenarios. However, we have the situation in Apache Cocoon where during site generation the project version is resolved to 2.4.1 (I haven't found out where this version comes from).
So we depend on spring-beans-2.0.2 which is resolved correctly and then Maven tries to get spring-core-2.4.1.
Would a log with option -X perhaps help you? (It's rather long)
> Invalid or problematic Spring POMS
> ----------------------------------
>
> Key: MEV-490
> URL: http://jira.codehaus.org/browse/MEV-490
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid POM
> Reporter: Carsten Ziegeler
>
> The Spring poms, for example spring-beans, version 2.0.2 use the following dependencies:
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>spring-core</artifactId>
> <version>${project.version}</version>
> </dependency>
> Which means, they are using variables in the poms. In some cases, these variables are resolved correctly, but in some cases however they are not, causing problems.
> Imho, it would be better to resolve variables for released poms to avoid any problems (or if variables are allowed, this is a maven bug then)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2782) Invalid or problematic Spring POMS
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2782?page=comments#action_85256 ]
Carlos Sanchez commented on MNG-2782:
-------------------------------------
yes, please provide an example as small as possible to see the incorrect behaviour
> Invalid or problematic Spring POMS
> ----------------------------------
>
> Key: MNG-2782
> URL: http://jira.codehaus.org/browse/MNG-2782
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Reporter: Carsten Ziegeler
>
> The Spring poms, for example spring-beans, version 2.0.2 use the following dependencies:
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>spring-core</artifactId>
> <version>${project.version}</version>
> </dependency>
> Which means, they are using variables in the poms. In some cases, these variables are resolved correctly, but in some cases however they are not, causing problems.
> Imho, it would be better to resolve variables for released poms to avoid any problems (or if variables are allowed, this is a maven bug then)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2782) Version property in dependencies is
not expanded correctly
Posted by "Grzegorz Slowikowski (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2782?page=comments#action_85338 ]
Grzegorz Slowikowski commented on MNG-2782:
-------------------------------------------
Look at this: http://jira.codehaus.org/browse/MNG-2653#action_79317
> Version property in dependencies is not expanded correctly
> ----------------------------------------------------------
>
> Key: MNG-2782
> URL: http://jira.codehaus.org/browse/MNG-2782
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Reporter: Carsten Ziegeler
>
> The Spring poms, for example spring-beans, version 2.0.2 use the following dependencies:
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>spring-core</artifactId>
> <version>${project.version}</version>
> </dependency>
> Which means, they are using variables in the poms. In some cases, these variables are resolved correctly, but in some cases however they are not, causing problems.
> Imho, it would be better to resolve variables for released poms to avoid any problems (or if variables are allowed, this is a maven bug then)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2782) Version property in dependencies is
not expanded correctly
Posted by "Carsten Ziegeler (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2782?page=comments#action_85347 ]
Carsten Ziegeler commented on MNG-2782:
---------------------------------------
Thanks for the link, Grzegorz. This sounds exactly like the problem we are experiencing.
So I think we can close this bug here.
> Version property in dependencies is not expanded correctly
> ----------------------------------------------------------
>
> Key: MNG-2782
> URL: http://jira.codehaus.org/browse/MNG-2782
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Reporter: Carsten Ziegeler
>
> The Spring poms, for example spring-beans, version 2.0.2 use the following dependencies:
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>spring-core</artifactId>
> <version>${project.version}</version>
> </dependency>
> Which means, they are using variables in the poms. In some cases, these variables are resolved correctly, but in some cases however they are not, causing problems.
> Imho, it would be better to resolve variables for released poms to avoid any problems (or if variables are allowed, this is a maven bug then)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2782) Version property in dependencies is not
expanded correctly
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2782?page=all ]
Carlos Sanchez updated MNG-2782:
--------------------------------
Summary: Version property in dependencies is not expanded correctly (was: Invalid or problematic Spring POMS)
> Version property in dependencies is not expanded correctly
> ----------------------------------------------------------
>
> Key: MNG-2782
> URL: http://jira.codehaus.org/browse/MNG-2782
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Reporter: Carsten Ziegeler
>
> The Spring poms, for example spring-beans, version 2.0.2 use the following dependencies:
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>spring-core</artifactId>
> <version>${project.version}</version>
> </dependency>
> Which means, they are using variables in the poms. In some cases, these variables are resolved correctly, but in some cases however they are not, causing problems.
> Imho, it would be better to resolve variables for released poms to avoid any problems (or if variables are allowed, this is a maven bug then)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira