Bug 1193103

Summary: maven: MNG-5663 regression in Maven 3.2.2
Product: [Fedora] Fedora Reporter: Martin Sivák <msivak>
Component: mavenAssignee: Mikolaj Izdebski <mizdebsk>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 21CC: akurtako, mizdebsk, msimacek, msrb
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 3.2.2-2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-25 10:02:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Sivák 2015-02-16 15:04:58 UTC
Description of problem:

Maven 3.2.2 has a nasty bug that breaks processing of dependencies that use BOM type POMs. This affects JBoss packages.

3.2.2 is the only version that is affected, any older or newer version is OK.

Can you please release an updated package for the currently stable Fedora (f21)?

Version-Release number of selected component (if applicable):

Fedora 21, maven 3.2.2

How reproducible:

Always, try depending on org.optaplanner:optaplanner-core:jar:6.1.0.Final for example.


Actual results:

Some JBoss dependencies will be missing: Failed to read artifact descriptor for org.optaplanner:optaplanner-core:jar:6.1.0.Final: Could not find artifact org.jboss.dashboard-builder:dashboard-builder-bom:pom:6.1.0.Final in central (http://repo.maven.apache.org/maven2) 

Expected results:

Build works the same as with maven 3.0.5 or 3.1.

Upstream bug:

http://jira.codehaus.org/browse/MNG-5663

Comment 1 Mikolaj Izdebski 2015-02-16 15:35:13 UTC
Confirmed. Reproducible on F21 with Maven 3.2.2. Not reproducible in rawhide with Maven 3.2.5

Comment 2 Mikolaj Izdebski 2015-02-16 16:09:36 UTC
I'll backport upstream fix for MNG-5663

Reproducer:
<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>foo</groupId>
  <artifactId>bar</artifactId>
  <version>1.2.3</version>
  <dependencies>
    <dependency>
      <groupId>org.optaplanner</groupId>
      <artifactId>optaplanner-core</artifactId>
      <version>6.1.0.Final</version>
    </dependency>
  </dependencies>
</project>

Comment 3 Mikolaj Izdebski 2015-02-16 16:10:18 UTC
Fixed in maven-3.2.2-2

Comment 4 Fedora Update System 2015-02-16 16:21:25 UTC
maven-3.2.2-2.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/maven-3.2.2-2.fc21

Comment 5 Mikolaj Izdebski 2015-02-16 21:23:38 UTC
Moving to QA for testing.

Comment 6 Mikolaj Izdebski 2015-02-25 10:02:41 UTC
I believe that this bug is fixed in maven-3.2.2-2,
which is available in updates for Fedora 21, so I am closing this bug now.

The build containing the fix can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=611763

Comment 7 Fedora Update System 2015-02-25 13:27:11 UTC
maven-3.2.2-2.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.