[#IDEADEV-26072] Multi-Module Project: Dependencies between Maven modules are not reflected as dependencies between IDEA modules

IDEA: Development

Multi-Module Project: Dependencies between Maven modules are not reflected as dependencies between IDEA modules

Created: 11 Apr 08 05:14 Updated: 17 Apr 08 17:36

Component/s:

Maven Integration

Fix Version/s:

Diana 8375, Selena 7.0.4

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

File Attachments:

demoPom.tgz (9 kb)

Image Attachments:

1. DependencyWarning.png
(156 kb)

2. Picture 3.png
(104 kb)

Environment:

Mac

Build:	7,782
Fixed in build:	7,807
Severity:	Medium

Description

« Hide

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.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Joshua Pollak - 11 Apr 08 05:17

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.

[ Permlink | « Hide ]

Anton Makeev - 11 Apr 08 15:47

Could you paste Parent:ModuleA:jar:0.0.1-SNAPSHOT pom here?

[ Permlink | « Hide ]

Joshua Pollak - 15 Apr 08 04:50

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?

[ Permlink | « Hide ]

Joshua Pollak - 15 Apr 08 04:53

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.