You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Graham Triggs (JIRA)" <ji...@codehaus.org> on 2005/06/15 12:48:26 UTC
[jira] Created: (MPIDEA-30) Allow multiproject processing that optionally doesn't link the modules
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPIDEA-30) Allow multiproject processing that optionally doesn't link the modules
Posted by "Graham Triggs (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIDEA-30?page=comments#action_45194 ]
Graham Triggs commented on MPIDEA-30:
-------------------------------------
Ooops - I've noticed that the source / patch that I've put up for linking source code to jars somehow makes IDEA forget how to deal with the source code within a module!!
God knows why, because the individual module files look correct... for now, if anyone wants to use my changes, use the older module.jelly that only links the dependencies as JARs, without the source code attachment.
> 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.6, 1.5
> 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 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPIDEA-30) Allow multiproject processing that optionally doesn't link the modules
Posted by "Graham Triggs (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIDEA-30?page=all ]
Graham Triggs updated MPIDEA-30:
--------------------------------
Attachment: module.jelly
Updated the module creation, so that when you link dependencies to the JARs in the repository instead of other modules, it generates the source link back to the module. This will then let you debug into the JAR (assuming that the sources you have locally are the same version as those used to build the JAR).
> 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.6, 1.5
> Reporter: Graham Triggs
> Priority: Minor
> Attachments: 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 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPIDEA-30) Allow multiproject processing that optionally doesn't link the modules
Posted by "Graham Triggs (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIDEA-30?page=comments#action_45120 ]
Graham Triggs commented on MPIDEA-30:
-------------------------------------
** Note that it is the 11 Kb module.jelly file that was uploaded on the 24th August that contains the additional fix to attach source directories to JAR dependencies that relate to modules in the reactor.
> 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.6, 1.5
> Reporter: Graham Triggs
> Priority: Minor
> Attachments: 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 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPIDEA-30) Allow multiproject processing that optionally doesn't link the modules
Posted by "Trygve Laugstol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIDEA-30?page=comments#action_45125 ]
Trygve Laugstol commented on MPIDEA-30:
---------------------------------------
For information on how to create patches for Maven please read this: http://maven.apache.org/maven2/developers/development-guide.html
> 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.6, 1.5
> 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 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPIDEA-30) Allow multiproject processing that optionally doesn't link the modules
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIDEA-30?page=comments#action_45122 ]
Brett Porter commented on MPIDEA-30:
------------------------------------
please create these as a patch against the original, not copies of the modified files.
> 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.6, 1.5
> Reporter: Graham Triggs
> Priority: Minor
> Attachments: 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 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPIDEA-30) Allow multiproject processing that optionally doesn't link the modules
Posted by "Graham Triggs (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIDEA-30?page=all ]
Graham Triggs updated MPIDEA-30:
--------------------------------
Attachment: ideapatch.txt
OK, I've uploaded a patch file.
Note that I've barely used Subversion (we use a commercial SCM), so I have no idea if this is OK - let me know if there is a problem.
> 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.6, 1.5
> 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 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPIDEA-30) Allow multiproject processing that optionally doesn't link the modules
Posted by "Wim Deblauwe (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIDEA-30?page=comments#action_41782 ]
Wim Deblauwe commented on MPIDEA-30:
------------------------------------
I could use this also. Please apply this patch.
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org