[ http://jira.codehaus.org/browse/MNG-325?page=comments#action_38370 ] Brett Porter commented on MNG-325: ----------------------------------
Dan, sorry I wasn't totally clear about my intentions. I think we might be doing additional work in this space in relation to a full repository app, just not in the scope of the current tool. I didn't think removing extend was really going to help here? Is there a pom coming through that is invalid? Also, I'd rather not remove dependencies if we can avoid it. But the main driver there is the amount of work involved, and that would be pushed to a bigger project as well. Some specific examples of things could be improved - eg filling in pom variables as you say (though not if the version is inherited) - if you have any examples, feel free to bring them up. > 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]
