[ 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
