You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Syte Beimin <sb...@betterbe.com> on 2007/07/17 16:37:50 UTC
Different approach to Multiple Module Projects
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
Re: Different approach to Multiple Module Projects
Posted by Mark Hobson <ma...@gmail.com>.
On 18/07/07, John Casey <jd...@commonjava.org> wrote:
> Not sure; I'm definitely not what you'd call a power user on
> Eclipse...I tend to learn only what I absolutely need to know in
> order to be productive with such tools, rather than really spending a
> lot of time optimizing my use of them...
>
> If that's possible, and could be coded into the plugin as a default
> behavior, then I'm definitely all ears...
Hmm, perhaps not - just had a look and access rules can be applied to
projects or jars within the build path, but not on individual source
folders within one project.
It's really down to eclipse to support hierarchical projects..
https://bugs.eclipse.org/bugs/show_bug.cgi?id=35973
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Different approach to Multiple Module Projects
Posted by John Casey <jd...@commonjava.org>.
Not sure; I'm definitely not what you'd call a power user on
Eclipse...I tend to learn only what I absolutely need to know in
order to be productive with such tools, rather than really spending a
lot of time optimizing my use of them...
If that's possible, and could be coded into the plugin as a default
behavior, then I'm definitely all ears...
-john
On Jul 18, 2007, at 11:12 AM, Mark Hobson wrote:
> On 18/07/07, John Casey <jd...@commonjava.org> wrote:
>> 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?
>
> Could this not be enforced used access rules?
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
Re: Different approach to Multiple Module Projects
Posted by Mark Hobson <ma...@gmail.com>.
On 18/07/07, John Casey <jd...@commonjava.org> wrote:
> 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?
Could this not be enforced used access rules?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Different approach to Multiple Module Projects
Posted by John Casey <jd...@commonjava.org>.
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: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
Re: Different approach to Multiple Module Projects
Posted by Syte Beimin <sb...@betterbe.com>.
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: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Different approach to Multiple Module Projects
Posted by Richard van Nieuwenhoven <ni...@cfc.at>.
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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Different approach to Multiple Module Projects
Posted by Stefano Bagnara <ap...@bago.org>.
Is this similar to what m2clipse plugin already do when I run "Enable
Maven2 support" on my right click menu for my eclipse project and then
run "update sources" ?
Stefano
Syte Beimin ha scritto:
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org