[jira] (MPIDEA-30) Allow multiproject processing that optionally doesn't link the modules

["Michael Osipov (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MPIDEA-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MPIDEA-30.
--------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> Allow multiproject processing that optionally doesn't link the modules
> ----------------------------------------------------------------------
>
>                 Key: MPIDEA-30
>                 URL: https://jira.codehaus.org/browse/MPIDEA-30
>             Project: Maven 1.x IDEA Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.5, 1.6
>            Reporter: Graham Triggs
>            Priority: Minor
>         Attachments: ideapatch.txt, module.jelly, 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 was sent by Atlassian JIRA
(v6.1.6#6162)