The only objection I have to this approach is that it sets you up for
introducing cyclic dependencies between modules. When all sources are
in the same project, and look like they might have come from the same
source tree, what's to stop you from crossing the boundaries imposed
by the POM's <dependencies/> and rendering the multimodule project
unbuildable?
-john
On Jul 17, 2007, at 11:30 AM, Syte Beimin wrote:
Thank you for pointing me in the right direction. I've submitted
the patch through the url you suggested.
I've made a little fix regarding the location of the test I
included. It's now in the src/test/java directory :)
So if anyone wants to try the new feature use the patch included in
http://jira.codehaus.org/browse/MECLIPSE-306
Syte Beimin
Richard van Nieuwenhoven wrote:
Hi,
The right place for maven-eclipse-plugin patch is
http://jira.codehaus.org/browse/MECLIPSE
i am also using many multi module projects, but i like it far more
to:
* checkout one multi module project
* start maven-eclipse-plugin
* import using the eclipse multi project importer all sub modules
from
this project as separate eclipse-projects
This works very good, just like using symbolic links in Unix.
Richard van Nieuwenhoven
Syte Beimin wrote:
First of all I hope this is the right place to send my patch to.
At my company we're used to check out an entire project from
subversion. So we'll get all the modules of a project in one eclipse
project. The eclipse plugin will create .project and .classpath
files
in each module directory. For easy checkout and maintainability I've
made a patch for the eclipse plugin. With the config
'<multiModule>true</multiModule>' the plugin now creates a .project
and .classpath file in the root of the multi module project. This
classpath has all the source and output directories setup so eclipse
put's it's outputs in the same directories (in the modules target
directories) where maven places them.
I'm sending this patch to this mailinglist because I suspect more
people would like to be able to check out their multi module
projects
in this manner instead of the circumvent way that is described on
http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html .
Perhaps it'll even make it into the next release who knows :)
Syte Beimin
Better.be
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
