[ http://jira.codehaus.org/browse/MNGECLIPSE-129?page=comments#action_66912 ]
Eugene Kuleshov commented on MNGECLIPSE-129: -------------------------------------------- Version stuff is working in the trunk code (0.0.10). For pom types please attach Eclipse project and all the poms needed to reproduce issue. Also specify when exactly error occurs (when resolving dependencies or when launching maven goals from within Eclipse). > dependency type from parent pom > ------------------------------- > > Key: MNGECLIPSE-129 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-129 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Components: Dependency Resolver > Versions: 0.0.9 > Environment: Eclipse: 3.1.1 > Reporter: Marek Bieganski > Assignee: Eugene Kuleshov > Priority: Minor > > > My pom contains dependencies like: > <parent> > <artifactId>xxx-parent</artifactId> > <groupId>com.xxx</groupId> > <version>HEAD-SNAPSHOT</version> > </parent> > ... > <dependency> > <groupId>com.xxx</groupId> > <artifactId>yyy</artifactId> > </dependency> > xxx-parent pom contains full yyy dependency info: > <dependency> > <groupId>com.xxx</groupId> > <artifactId>yyy</artifactId> > <version>HEAD-SNAPSHOT</version> > <type>ejb</type> > </dependency> > Problem occurs when <type>ejb</type> is declared in parent pom, and no <type> > is declared in child pom. > Only error message i got is: > 06-05-30 15:32:49 CEST: Project build error Failed to validate POM > Workaround is to redeclare <type>ejb</type> in child pom, but AFAIK if no > type is declared, it should be inherited from parent -- 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
