[
http://jira.codehaus.org/browse/MECLIPSE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113969
]
Barrie Treloar edited comment on MECLIPSE-32 at 11/15/07 5:15 PM:
------------------------------------------------------------------
I tried using -r to specify the includes and it is finding projects that are
not defined as modules in my pom.
I tried an equivalence test:
i.e.
mvn eclipse:eclipse
should be equivalent to
mvn eclipse:eclipse -r -Dmaven.reactor.includes=pom.xml
also tried
mvn eclipse:eclipse -r
'-Dmaven.reactor.includes=\full\windows\path\to\pom.xml'
(which required quoting to avoid backslash issues.
But neither of the -r options work.
I also can find no documentation on the -r option. Which makes me reluctant to
use this solution here and on MECLIPSE-158
For some reason the reactor is trying to locate a much older version of the pom.
Although now I am not convinced the quoting of the arguments is correct as it
probably pulling something out of the local m2 repository. Other commands
(like help:effective-pom) are failing with
[INFO] Cannot execute mojo: effective-pom. It requires a project with an
existing pom.xml, but the build is not using one.
was:
I tried using -r to specify the includes and it is finding projects that are
not defined as modules in my pom.
I tried an equivalence test:
i.e.
mvn eclipse:eclipse
should be equivalent to
mvn eclipse:eclipse -r -Dmaven.reactor.includes=pom.xml
also tried
mvn eclipse:eclipse -r
'-Dmaven.reactor.includes=\full\windows\path\to\pom.xml'
(which required quoting to avoid backslash issues.
But neither of the -r options work.
I also can find no documentation on the -r option. Which makes me reluctant to
use this solution here and on MECLIPSE-229
> Allow for forcing the creation of direct project references for dependencies
> ----------------------------------------------------------------------------
>
> Key: MECLIPSE-32
> URL: http://jira.codehaus.org/browse/MECLIPSE-32
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: multiproject
> Affects Versions: 2.0
> Reporter: Barry Kaplan
>
> For some thirdparty dependencies, it is common (for me at least) that an
> eclipse project for that dependency does/will exist in the workspace. It
> would be nice if dependencies in eclipse projects can be forced to use a
> direct project reference. eg:
> <dependency>
> <groupId>backport-util-concurrent</groupId>
> <artifactId>backport-util-concurrent</artifactId>
> <version>2.0_01_pd</version>
> <scope>runtime</scope>
> <properties>
> <property name="eclipse.dependencyType" value="XXXX"/>
> </properties>
> </dependency>
> Where XXXX can be:
> - 'project' -- always create a project reference
> - 'jar' -- always create a jar reference as in MNG-955
> - 'auto' -- the behavior prior to MNG-955
--
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
