[ http://jira.codehaus.org/browse/MECLIPSE-22?page=all ]
Jason van Zyl moved MNG-1078 to MECLIPSE-22:
--------------------------------------------
Component: (was: maven-eclipse-plugin)
Workflow: jira (was: Maven)
Key: MECLIPSE-22 (was: MNG-1078)
Project: Maven 2.x Eclipse Plugin (was: Maven 2)
> Exclude pom-type dependencies in eclipse projects
> -------------------------------------------------
>
> Key: MECLIPSE-22
> URL: http://jira.codehaus.org/browse/MECLIPSE-22
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Reporter: Daniel Krisher
> Assignee: Brett Porter
> 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]
