You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vikash Ramanlal (JIRA)" <ji...@codehaus.org> on 2006/03/17 10:08:11 UTC
[jira] Created: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
-------------------------------------------------------------------------------------------------------------------------------------
Key: MIDEA-39
URL: http://jira.codehaus.org/browse/MIDEA-39
Project: Maven 2.x Idea Plugin
Type: Improvement
Versions: 2.0
Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
Reporter: Vikash Ramanlal
Priority: Minor
When I generate my idea files using "mvn idea:idea", all works fine.
However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Commented: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Andrew Perepelytsya (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91944 ]
Andrew Perepelytsya commented on MIDEA-39:
------------------------------------------
Almost ;) The above behavior might be a step forward, but for now just being able to resolve the reactor projects and linking to them is all that is needed.
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assigned To: Brett Porter
> Priority: Minor
> Fix For: 2.1
>
> Attachments: module-dependencies.patch, mule-module-ognl.iml_false, mule-module-ognl.iml_true
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Commented: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Andrew Perepelytsya (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=comments#action_62069 ]
Andrew Perepelytsya commented on MIDEA-39:
------------------------------------------
I don't think that's a 100% solution. When I have 30 something modules in the project I can generate idea files as you said, once. Then, when 1 module is added, I really want to have an option whether to generate it with the libs or with project dependencies. I guess poms contain all the information requried to have this kind of functinality.
To make things worse, some latest IDEA builds have HUGE problems if you have both library jars and project dependencies (sources), resulting in debug breakpoints being skipped altogether (read, impossible to debug anything).
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Type: Improvement
> Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assignee: Brett Porter
> Priority: Minor
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Closed: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MIDEA-39.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.1
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assigned To: Brett Porter
> Priority: Minor
> Fix For: 2.1
>
> Attachments: module-dependencies.patch
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Commented: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91698 ]
Dennis Lundberg commented on MIDEA-39:
--------------------------------------
Is there nobody out there who can confirm or deny that this is working in 2.1-SNAPSHOT?
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assigned To: Brett Porter
> Priority: Minor
> Attachments: module-dependencies.patch
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Commented: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91936 ]
Dennis Lundberg commented on MIDEA-39:
--------------------------------------
Andrew,
I think you are trying to use the wrong parameter here. The configuration parameter to switch between module dependencies and libraries is called "linkModules". That is what this issue is about. See snippet from the source of the plugin below:
{code}
/**
* Whether to link the reactor projects as dependency modules or as libraries.
*
* @parameter expression="${linkModules}" default-value="true"
*/
private boolean linkModules;
{code}
Here's the corresponding source for "useFullNames":
{code}
/**
* Whether to use full artifact names when referencing libraries.
*
* @parameter expression="${useFullNames}" default-value="false"
*/
private boolean useFullNames;
{code}
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assigned To: Brett Porter
> Priority: Minor
> Fix For: 2.1
>
> Attachments: module-dependencies.patch, mule-module-ognl.iml_false, mule-module-ognl.iml_true
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Commented: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89104 ]
Dennis Lundberg commented on MIDEA-39:
--------------------------------------
This is working for me using the latest 2.1-SNAPSHOT version of this plugin and IDEA 5.1.2. Can you please try it.
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assigned To: Brett Porter
> Priority: Minor
> Attachments: module-dependencies.patch
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Commented: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Andrew Perepelytsya (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91933 ]
Andrew Perepelytsya commented on MIDEA-39:
------------------------------------------
I don't understand the point of the last comment. That is exactly what this issue is about, and that behavior is a problem. I've rebuild the plugin from trunk, but no, nothing is fixed. In fact, the only difference between having useFullNames on and off is the linkage of sources jar (?!). I'm attaching 2 outputs from idea:module run with the above setting on and off, it always generates links to jars from inside the module.
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assigned To: Brett Porter
> Priority: Minor
> Fix For: 2.1
>
> Attachments: module-dependencies.patch, mule-module-ognl.iml_false, mule-module-ognl.iml_true
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Commented: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Andrew Perepelytsya (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91939 ]
Andrew Perepelytsya commented on MIDEA-39:
------------------------------------------
Thanks for the clarification, Dennis.
Then, l saw this linkModules and it was true by default, which haven't generated the desired output. Why do I think it should? E.g. consider a reactor project where your CWD is somewhere down the path in a child. If I modify the root pom to use a different version of e.g. plugin, the project I'm currently in properly resolves all poms upwards to the root (they are all available on the disk), and actually picks up the change. I don't have to run from the root.
This leads me to the conclusion that similar behavior should be made available to the IDEA plugin.
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assigned To: Brett Porter
> Priority: Minor
> Fix For: 2.1
>
> Attachments: module-dependencies.patch, mule-module-ognl.iml_false, mule-module-ognl.iml_true
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Updated: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Danie Roux (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=all ]
Danie Roux updated MIDEA-39:
----------------------------
Attachment: module-dependencies.patch
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Type: Improvement
> Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assignee: Brett Porter
> Priority: Minor
> Attachments: module-dependencies.patch
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Closed: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=all ]
Brett Porter closed MIDEA-39:
-----------------------------
Assign To: Brett Porter
Resolution: Won't Fix
if you generate everything togehter, they get linked.
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Type: Improvement
> Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assignee: Brett Porter
> Priority: Minor
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Reopened: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=all ]
Brett Porter reopened MIDEA-39:
-------------------------------
ok, perhaps we could do a USD-ish thing, but not for 2.0.
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Type: Improvement
> Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assignee: Brett Porter
> Priority: Minor
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Updated: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Andrew Perepelytsya (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Perepelytsya updated MIDEA-39:
-------------------------------------
Attachment: mule-module-ognl.iml_false
mule-module-ognl.iml_true
SVN revision tested: 525253
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assigned To: Brett Porter
> Priority: Minor
> Fix For: 2.1
>
> Attachments: module-dependencies.patch, mule-module-ognl.iml_false, mule-module-ognl.iml_true
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Commented: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Arik Kfir (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91703 ]
Arik Kfir commented on MIDEA-39:
--------------------------------
This is definitly working for me in 2.1-SNAPSHOT. Caveat is to run "mvn idea:idea" in the multi-module root; if you run it inside one of the modules, inter-module dependencies indeed do not work (as they are not in the reactor I believe).
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assigned To: Brett Porter
> Priority: Minor
> Attachments: module-dependencies.patch
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Commented: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91943 ]
Dennis Lundberg commented on MIDEA-39:
--------------------------------------
So if I understand you correctly, you want to be able to run "mvn idea:module" somewhere below the parent pom. That should then update the IDEA module regarding dependencies that have been modified in the parent pom. If that is not working for you I suggest that you open another issue for that.
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assigned To: Brett Porter
> Priority: Minor
> Fix For: 2.1
>
> Attachments: module-dependencies.patch, mule-module-ognl.iml_false, mule-module-ognl.iml_true
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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
[jira] Commented: (MIDEA-39) In a multi-module project, idea plugin
should generate module dependencies instead of creating libs with
references to the repository
Posted by "Sanjiv Jivan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MIDEA-39?page=comments#action_71001 ]
Sanjiv Jivan commented on MIDEA-39:
-----------------------------------
If useFullNames = true, even when I generate everything the module depency shows up as a library dependency. If useFullNames=false, the project files get correctly generated with module dependency.
> In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-39
> URL: http://jira.codehaus.org/browse/MIDEA-39
> Project: Maven 2.x Idea Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2
> Reporter: Vikash Ramanlal
> Assigned To: Brett Porter
> Priority: Minor
> Attachments: module-dependencies.patch
>
>
> When I generate my idea files using "mvn idea:idea", all works fine.
> However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository.
> Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project.
--
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