Allow multiproject processing that optionally doesn't link the modules
----------------------------------------------------------------------
Key: MPIDEA-30
URL: http://jira.codehaus.org/browse/MPIDEA-30
Project: maven-idea-plugin
Type: Improvement
Versions: 1.5, 1.6
Reporter: Graham Triggs
Priority: Minor
Attachments: module.jelly, plugin.properties
The way our environment is setup, each 'module' is a distinct unit, that is
always built against versioned dependencies in the repository.
In most cases, it actually benefits us to not link module dependencies to other
modules, but we still want the convenience of doing a single idea:multiproject
operation to generate all the module files, and reference them from a single
workspace. (We've also seen problems with debugging in idea caused by module
dependency linking, where one module is in an unreleased, modified state, and
we have to work on fixes to another module being built against a previous
released version of the first module).
I've amended the plugin.properties and v4 module.jelly, to include an
additional property - maven.idea.project.link.modules. By default, it is set to
true, and the behaviour is unchanged from the current releases (dependent
modules are linked when attaining multiproject). Setting
maven.idea.project.link.modules to false disables the module linking, and the
module references the versioned JAR from the repository instead.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
