[ http://jira.codehaus.org/browse/MNG-325?page=comments#action_37800 ]
John Casey commented on MNG-325:
--------------------------------
If these are maven-1 pom's and they extend something, we probably can't
reliably convert it to a maven-2 pom, since the <extends/> element uses local
filesystem paths.
In certain (probably rare) cases, if the parent is specified as:
${maven.repo.local}/myGroup/poms/myArtifact-version.pom
then it's possible that we may be able to extract the parent pom info and look
it up in the repository. This is not currently enabled, however.
I'll look into the specific cases for xfire, and we can probably add some
measure of interpolation, but be aware that the extends stuff will probably
never work reliably.
> Do something about interpolated values in dependencies
> ------------------------------------------------------
>
> Key: MNG-325
> URL: http://jira.codehaus.org/browse/MNG-325
> Project: m2
> Type: Sub-task
> Reporter: Dan Diephouse
> Assignee: John Casey
>
>
> In the xfire poms, we extend the parent and have ${pom.currentVersion} in the
> version field for a lot of the dependencies. M2 chokes on these. Maybe these
> dependencies can be thrown out? Maybe pom.currentVersion can be filled in
> automatically?
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
