[MNG-5536] Wrong runtime classpath if inheriting dependencies specified by profile from parent

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Not A Problem
• Affects Version/s: 3.1.1
• Component/s: Profiles
• Environment: Win
• Assignee: Unassigned
• Reporter: Tibor Digana
• Created: 17/Nov/13 17:11
• Updated: 17/Apr/14 04:45
• Resolved: 17/Apr/14 04:45

Description

The module DAO-BOM(pom) defines dependency within a profile.
Other module webapp(war) which indirectly inherits from DAO-BOM does not see such dependency hibernate-core-4.2.6.Final.jar and dependency which was not excluded hibernate-commons-annotations-4.0.2.Final.jar

Since the failure results in dependency and war plugin, it looks like the bug is in Maven core and related to profiles.

I found this issue when I examied the workaround for
https://jira.codehaus.org/browse/MNG-2205

The problem is that the build result is different in Maven 2.2.1 and Maven 3.1.1 in webapp module.

The Maven 2.2.1 works as expected.

There are two issues with Maven 3.1.1 :
+ Maven 3 ignored two Hibernate runtime artifacts which I expect in WAR file;
+ classpath produced by maven-dependency-plugin:build-classpath does not have those two runtime artifacts if includeScope=runtime. See the webapp POM.

The Zip file contains the project and four text files.