You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Xavier Hanin (JIRA)" <ji...@apache.org> on 2007/06/29 09:42:04 UTC
[jira] Updated: (IVY-550) pom.groupId is not recognized in maven 2
pom parser
[ https://issues.apache.org/jira/browse/IVY-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xavier Hanin updated IVY-550:
-----------------------------
Description:
Maven 2 allows to use ${pom.groupId} as a reference to the pom group id when declaring dependencies. This property is not recognized by Ivy, causing error like:
module not found: [ ${pom.groupId} | databinder-models | 1.1-SNAPSHOT ]
was:
Maven 2 allows to use ${pom.groupId} as a reference to the pom group id when declaring dependencies. This property is not recognized by Ivy, causing error like:
{code}
module not found: [ ${pom.groupId} | databinder-models | 1.1-SNAPSHOT ]
{code}
> pom.groupId is not recognized in maven 2 pom parser
> ---------------------------------------------------
>
> Key: IVY-550
> URL: https://issues.apache.org/jira/browse/IVY-550
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-1
> Reporter: Xavier Hanin
> Fix For: 2.0.0-alpha-2
>
>
> Maven 2 allows to use ${pom.groupId} as a reference to the pom group id when declaring dependencies. This property is not recognized by Ivy, causing error like:
> module not found: [ ${pom.groupId} | databinder-models | 1.1-SNAPSHOT ]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.