History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEADEV-25593
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Normal Normal
Assignee: Anton Makeev
Reporter: Ben Gidley
Votes: 3
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
IDEA: Development

Dependency Management section is not cascading correctly

Created: 05 Mar 08 14:04   Updated: 28 Mar 08 17:27
Component/s: Maven Integration
Fix Version/s: Selena 7.0.4

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Zip Archive PomProblemSample.zip (92 kb)

Issue Links:
Relates
This issue relates to:
IDEADEV-25594 Parent POM properties are not working... Normal Resolved
 

Build: 7,744
Fixed in build: 8,256
Severity: High


 Description  « Hide
In Maven you can usually set a project up so that the parent POM dependency management sets excludes for all child projects. This works with both POM and jar dependencies.

In IntelliJ 7.0.2 this works perfectly.

In build 7744 it appears not to be matching the dependency management to the dependency in the child POM.

In the attached project the child does not pick up the version at all from the parents dependency management section. This only impacts POM dependencies. Adding the version explicitly works around this project but loses the exclusions from the parent POM.

The 'correct' behaviour is seen in 7.0.2



 All   Comments   Work Log   Change History      Sort Order:
Ben Gidley - 23 Mar 08 15:03
I have created a test case and logged this with the maven embedder project - http://jira.codehaus.org/browse/MNG-3479