[ http://jira.codehaus.org/browse/MAVEN-1265?page=comments#action_67666 ]
Lukas Theussl commented on MAVEN-1265: -------------------------------------- I think this is adequately explained in the scripting guide: http://maven.apache.org/maven-1.x/reference/scripting.html, see sections 'Accessing the Current Project' and 'Using Dependencies'. > getDependencyPath fails for nonstandard types > --------------------------------------------- > > Key: MAVEN-1265 > URL: http://jira.codehaus.org/browse/MAVEN-1265 > Project: Maven > Type: Bug > Components: core > Versions: 1.0-rc2 > Environment: WinXP, cygwin > Reporter: Matt Johnson > Assignee: Brett Porter > Fix For: 1.0-rc3 > > > When attempting to retrieve dependency path information, > ${pom.getDependencyPath('my.dependency.id')} is empty for dependencies which > have a nonstandard <type>. > Workaround is to iterate over ${pom.artifacts} and compare dependency id's to > the one you're after. -- 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
