The following comment has been added to this issue:
Author: Graham Triggs
Created: Wed, 28 Jul 2004 10:30 AM
Body:
Another thought - it should only make dependencies between projects when the
dependency in the project.xml is a SNAPSHOT.
If you are referencing a numbered version, then the assumption should be that you are
referencing a JAR that was created with source code that is out of date compared to
your current working project.
(This can also relate back to the need to have source code JARs in the repository)
Only if your project.xml references a SNAPSHOT dependency can you deduce that the
current working source - and therefore a module dependency - is valid.
(Although this could be overridden - you may in fact be referencing a SNAPSHOT that is
provided by someone else through a central repository, and so your project would in
that case depend on the copy in your local repository - expecting you to update via
Maven where necessary)
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPIDEA-7?page=comments#action_22452
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPIDEA-7
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPIDEA-7
Summary: IDEA .iml file assumes dependencies with same groupId as current project
to be IDEA modules
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-idea-plugin
Assignee: Brett Porter
Reporter: Sverre Eplov
Created: Wed, 30 Jun 2004 4:01 AM
Updated: Wed, 28 Jul 2004 10:30 AM
Environment: Maven RC4, IDEA plugin 1.5
Description:
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.
> >
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
