Project
IntelliJ IDEA
Priority
Normal
Type
Bug
Fix versions
No Fix versions
State
Fixed
Assignee
Anton Makeev
Subsystem
Maven Integration
Affected versions
No Affected versions
Fixed in build
108.65  
  • Created by   Joshua Pollak
    3 years ago (11 Apr 2008 06:14)
  • Updated by   root
    2 years ago (17 Jan 2010 20:59)
  • Jira: IDEADEV-26072
    (history, comments)
 
IDEA-43508 Multi-Module Project: Dependencies between Maven modules are not reflected as dependencies between IDEA modules
0
Issue is visible to: All Users
  The issue is visible to the selected user group only
I just tried EAP 7782, and now when my multi-project pom is imported, the dependancies between the modules within it are not recognized. Specifically if I have:

Parent
+
ModuleA
+
ModuleB

And ModuleB depends on ModuleA, I import the Parent/pom.xml file.

When it is finished, I see "Warning: Unresolved Dependency: Parent:ModuleA:jar:0.0.1-SNAPSHOT in the "Maven Import" window.

Also, in the Project Settings screen

Parent:ModuleA-0.0.1-SNAPSHOT

is listed as a dependancy of moduleB in instead of the internal IDEA ModuleA.



Environment: Mac

Issue was resolved
Comments (4)
 
History
 
Linked Issues (?)
 
Joshua Pollak
  Joshua Pollak
11 Apr 2008 06:17
3 years ago
Also, when I file a new bug, I get a screen that says:

HTTP Status 404 - No view for result [error] exists for action [ViewIssue]

type Status report

message No view for result [error] exists for action [ViewIssue]

description The requested resource (No view for result [error] exists for action [ViewIssue]) is not available.

Instead of something user friendly, so I didn't know this bug was successfully filed.
Anton Makeev
  Anton Makeev
11 Apr 2008 16:47
3 years ago
Could you paste Parent:ModuleA:jar:0.0.1-SNAPSHOT pom here?
Joshua Pollak
  Joshua Pollak
15 Apr 2008 05:50
3 years ago
Attached is an entire demo project, along with a screen capture of what I see when I import it.

This project has 3 modules: A, B, and C.

A depends on nothing, B depends on A, and C depends on A and B. In addition, B uses the build-helper plugin to add an additional source path (src2) , with another source path (src3) controlled by an optional profile. I see that moduleB correctly added src and src2, but did not add src3, which is the behavior I would expect.

However, I find it strange that all three modules have directories underneath them with the same name as themselves. In the screen shot, why aren't 'src', 'src2', and 'src3' directly under the moduleB module?
Joshua Pollak
  Joshua Pollak
15 Apr 2008 05:53
3 years ago
Attached is another screenshot showing the dependency warnings in the background (like in the previous screenshot), but with the module settings in the foreground, showing the module is a dependency of the module. I'm not sure which is correct, perhaps the warning should be supressed.