[jira] Updated: (MIDEA-39) In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository

["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