maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <>
Subject [jira] Commented: (MEV-490) Invalid or problematic Spring POMS
Date Wed, 17 Jan 2007 09:07:40 GMT
    [ ] 
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

Would a log with option -X perhaps help you? (It's rather long)

> Invalid or problematic Spring POMS
> ----------------------------------
>                 Key: MEV-490
>                 URL:
>             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:
For more information on JIRA, see:


View raw message