You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2007/01/17 18:28:40 UTC

[jira] Moved: (MNG-2782) Invalid or problematic Spring POMS

     [ 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