You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Daniel Krisher <da...@gmail.com> on 2005/10/03 21:53:19 UTC
[m2] Eclipse plugin and pom-type dependencies
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?
--
Daniel Krisher
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Eclipse plugin and pom-type dependencies
Posted by John Casey <jd...@commonjava.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sounds like a bug in the maven-eclipse-plugin...can you file a jira at
http://jira.codehaus.org/Browse/MNG and make sure you specify it as
being a problem with the eclipse plugin? It should be in the modules list.
Thanks,
john
Daniel Krisher wrote:
| 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?
|
| --
| Daniel Krisher
|
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
| For additional commands, e-mail: users-help@maven.apache.org
|
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFDQZaeK3h2CZwO/4URAn2iAJ0YgSRegY7L5LJNvsDxEYbd2Wi2VgCcD4tf
FEualslur9IhEJxaei3Pg00=
=3MUL
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org