[ http://jira.codehaus.org/browse/MPIDEA-7?page=comments#action_40886 ] Geoffrey commented on MPIDEA-7: -------------------------------
The eclipse plugin allows you to choose which are managed by eclipse by adding this property to a dependency in the pom: <eclipse.dependency>true</eclipse.dependency> > IDEA .iml file assumes dependencies with same groupId as current project to > be IDEA modules > ------------------------------------------------------------------------------------------- > > Key: MPIDEA-7 > URL: http://jira.codehaus.org/browse/MPIDEA-7 > Project: maven-idea-plugin > Type: Bug > Environment: Maven RC4, IDEA plugin 1.5 > Reporter: Sverre Eplov > Attachments: diff.txt > > > This is the mail describing the problem and suggested solutions > br > /Sverre > --------------------------------------- > (From Brett Porter) > Actually, this should probably only be done when you run > idea:multiproject, and then only for projects in that build rather > than automatically assuming you will import your external project > modules. > But wither way, definitely file a JIRA issue for this. > Cheers, > Brett > On Tue, 29 Jun 2004 15:46:44 +0200, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > Hi Again, > > > > I've done some digging into the plugin and found, that the module.jelly > > which > > generates the .iml file *does* sort the jar files into external and internal > > module vs. module-libraries. > > > > I would suggest a plugin property which should be tested against in the > > module.jelly file, so it is possible to select wether jar files with same > > groupId as the current project are registered as module or module-library in > > the generated .iml file. > > > > The property could be something like > > > > maven.idea.project.groupmodules=<true | false> > > > > The default value for the property could leave the plugin with the current > > behaviour, thus backward compability is secured. > > > > How sounds ? > > > > Br, > > /Sverre Eplov > > > > Citat [EMAIL PROTECTED]: > > > > > > > > > Hi all, > > > > > > I'm using the IDEA plugin to generate the IDEA IDE project files. > > > > > > The projects we're doing consists of a number of artifacts (jar, war, > > > ejb-jar > > > > > > files e.t.c.) grouped by groupId to indicate that they belong to the same > > > application. > > > > > > When the IDEA plugin generates the .iml file, it seems to distinguish > > > between > > > > > > artifacts belonging to the same groupId as the project itself and > > > artifacts > > > from other groupId's. > > > > > > A dependency to a jar file "cabin-utility" with the same groupId as the > > > project > > > itself generates following entry in the .iml file: > > > > > > <orderEntry type="module" module-name="cabin-utility"> > > > </orderEntry> > > > > > > whereas a dependency on a jar file with a groupId different from the > > > project > > > > > > generates this entry: > > > > > > <orderEntry type="module-library"> > > > <library name="ejb"> > > > <CLASSES> > > > <root > > > url="jar://c:/java_devenv/maven/repository\ejb\jars\ejb-2.0.jar!/"> > > > </root> > > > </CLASSES> > > > <JAVADOC> > > > </JAVADOC> > > > <SOURCES> > > > </SOURCES> > > > </library> > > > </orderEntry> > > > > > > The problem is, that any dependency on any jar file should be treated > > > as "external", since projects with same groupId is not checked out at the > > > developer workstation, thus resulting in IDEA missing jar files when the > > > project is opened. > > > -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
