[
http://jira.codehaus.org/browse/MNG-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176782#action_176782
]
Jörg Hohwiller commented on MNG-2576:
-------------------------------------
Thanks for the hints.
I updated to official 2.1.0.
However I am clueless with "-r" whatever it should do. It is definitively NOT
what I described in MNG-3377.
I also tried -pl which is sort of not-intuitive. I have to supply the full path
down to my module.
The showcase of doing a eclipse:eclipse on a single module but having the
project in the reactor so project dependencies are not pointing to jars did NOT
work.
I did
cd mmm (toplevel)
mvn eclipse:eclipse
cd mmm-util/mmm-util-core
mv .classpath .classpath.ori
cd ../..
mvn eclipse:eclipse -pl mmm-util/mmm-util-pojo
cd mmm-util/mmm-util-core
diff .classpath .classpath.ori
I get:
12c12
< <classpathentry kind="var"
path="M2_REPO/net/sf/m-m-m/mmm-util-core/1.0.3-SNAPSHOT/mmm-util-core-1.0.3-SNAPSHOT.jar"
sourcepath="M2_REPO/net/sf/m-m-m/mmm-util-core/1.0.3-SNAPSHOT/mmm-util-core-1.0.3-SNAPSHOT-sources.jar"/>
---
> <classpathentry kind="src" path="/mmm-util-core"/>
All I wanted in MNG-3377 is
cd mmm-util/mmm-util-core
mvn -r eclipse:eclipse
and have the project dependencies as build from toplevel.
Please note eclipse:eclipse is just one usecase here.
Is this a bug or shall I reopen MNG-3377 because it is no duplicate and this
issue is something different that is no use for me?
> Make Like Reactor Mode
> ----------------------
>
> Key: MNG-2576
> URL: http://jira.codehaus.org/browse/MNG-2576
> Project: Maven 2
> Issue Type: New Feature
> Components: Command Line, Reactor and workspace
> Reporter: Kenney Westerhof
> Assignee: Dan Fabulich
> Fix For: 2.1.0-M1
>
>
> Add a commandline option to enable maven to expand the reactor scope to find
> projects that are dependencies
> of the projects currently in the reactor, and add them.
> Currently only the current project and child projects are included in the
> reactor search. I'm proposing
> to add a commandline switch that lets maven check parent directories to find
> the root of the project tree,
> and then do a normal reactor scan, only adding projects that would normally
> not be added if they're needed
> as dependencies of the projects that would normally be built.
> Here's a sample project tree:
> * root
> ** p1
> *** c1 (depends on p2)
> ** p2 (depends on c2)
> ** p3
> *** c2
> And a sample algorithm:
> - When building c1, the reactor would contain [c1].
> - Maven would check p1, then root, etc, using the <parent> tags (without the
> versions!)
> to see if the project is still in the current reactor.
> - It would then create a second list of projects (reactor2) containing ALL
> projects, using the newly discovered root: [root, p1, c2, p2].
> - remove all projects from reactor2 contained in reactor: reactor2 = [root,
> p1, p2]
> - resolve all direct dependencies for all projects in reactor in reactor2 and
> add them to reactor, taking versions into account: reactor = [p2, c1]
> - repeat previous step until all projects have their dependencies resolved
> from reactor 2. first iteration would yield reactor = [c2, p2, c1],
> next iteration would stop since c1 doesn't have any dependencies present in
> reactor2.
> This would ensure that when some local project's sources have changed,
> they'll be incorporated
> in the build, regardless of where you build. So you don't have to do a
> reactor build each time you change more
> than 1 project, and you don't have to remember which projects you changed and
> build them in the correct order
> yourself, manually.
--
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
