You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/01/27 01:53:49 UTC

[jira] Closed: (OPENEJB-461) Workaround for maven misresolving ${pom.version}

     [ https://issues.apache.org/jira/browse/OPENEJB-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed OPENEJB-461.
--------------------------------

    Resolution: Fixed

done in rev 500438.  Hopefully this will reduce rather than increase the number of build problems.

> Workaround for maven misresolving ${pom.version}
> ------------------------------------------------
>
>                 Key: OPENEJB-461
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-461
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: build
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: 3.0
>
>
> see http://jira.codehaus.org/browse/MNG-2796
> The geronimo build has been having problems due to maven resolving ${pom.version} in dependencies which should be 3.0-incubating-SNAPSHOT to the timestamped version of the current pom rather than trying to resolve it for the dependency itself.  
> The workaround seems to be to define a ${version} property ourselves.  jdillon did this quite a while ago in the geronimo build to workaround lots of similar issues.

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