You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gordon Henriksen (JIRA)" <ji...@codehaus.org> on 2006/04/01 03:39:44 UTC
[jira] Closed: (MECLIPSE-88) mvn eclipse:eclipse shouldn't require
install of internal dependencies?
[ http://jira.codehaus.org/browse/MECLIPSE-88?page=all ]
Gordon Henriksen closed MECLIPSE-88:
------------------------------------
Resolution: Duplicate
This is a duplicate of MECLIPSE-3.
> mvn eclipse:eclipse shouldn't require install of internal dependencies?
> -----------------------------------------------------------------------
>
> Key: MECLIPSE-88
> URL: http://jira.codehaus.org/browse/MECLIPSE-88
> Project: Maven 2.x Eclipse Plugin
> Type: Improvement
> Environment: Mac OS X 10.4.5
> Windows XP SP2
> Reporter: Gordon Henriksen
>
>
> When referencing a dependency internal to the source tree, the eclipse plugin requires that the project first be installed. This is at its most preposterous when creating a brand new project and configuring it for development in Eclipse; we have to install it before we can even start writing code. This seems premature.
> For instance, create the following:
> mkdir example
> cat <<'EOT' >pom.xml
> <project>
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.example</groupId>
> <artifactId>example</artifactId>
> <version>1.0-SNAPSHOT</version>
> <packaging>pom</packaging>
> <modules>
> <module>my-lib</module>
> <module>my-app</module>
> </modules>
> </project>
> EOT
> mvn archetype:create -DgroupId=com.example -DartifactId=my-lib
> mvn archetype:create -DgroupId=com.example -DartifactId=my-app
> Add to my-app/pom.xml:
> <dependency>
> <groupId>com.example</groupId>
> <artifactId>my-lib</artifactId>
> </dependency>
> Run:
> mvn eclipse:eclipse
> And watch the fireworks. It seems awfully silly, but you have to mvn install for my-lib first. (Mind you, this makes complete sense for external dependencies, just not for those that are also going into Eclipse.)
> I'm not sure if this is fixable, or if there's an existing workaround that I've not been able to find; I haven't gotten any responses on the mailing list. I also apologize if it's a duplicate; I did comb the summaries before I filed, and I didn't see anything similar.
--
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