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 <[EMAIL PROTECTED]> 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: [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
