[ http://jira.codehaus.org/browse/MNG-1078?page=comments#action_48427 ]
Daniel Krisher commented on MNG-1078: ------------------------------------- I think this is a dup of MNG-578 > Exclude pom-type dependencies in eclipse projects > ------------------------------------------------- > > Key: MNG-1078 > URL: http://jira.codehaus.org/browse/MNG-1078 > Project: Maven 2 > Type: Bug > Components: maven-eclipse-plugin > Reporter: Daniel Krisher > Priority: Minor > > > From <maven-users>: > I have a set of 'third-party' jars that are all part of a library > developed in-house. Most of the projects I work on use all of the > jars from this library, so I put together a simple POM that depends on > all of them. I then add this POM as a dependency of my project: > <dependency> > <groupId>...</groupId> > <artifactId>...</artifactId> > <version>...</version> > <type>pom</type> > </dependency> > This works fine for dependency resolution, however the eclipse plugin > produces a project configuration that includes the .pom as a > dependency. Eclipse does not like this and will not build the project > until the .pom dep. is removed... Should .poms be excluded when > generating the eclipse project? -- 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]