Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 900871 (JBPAPP6-1339)

Summary: Some artifacts of EAP 6.0.1.ER1 depend on old jUnit 4.10-redhat-1 (should be -2)
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ondřej Žižka <ozizka>
Component: BuildAssignee: Ondřej Žižka <ozizka>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: dosoudil, ozizka, rsvoboda
Target Milestone: ---   
Target Release: EAP 6.0.1   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-1339
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-19 13:30:20 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:
Bug Depends On: 900874, 900875    
Bug Blocks: 900856    

Description Ondřej Žižka 2012-09-10 13:21:19 UTC
project_key: JBPAPP6

When building the javadoc from EAP, using  ER1 tag, and a command 

AS7/ozizka-git/build$ mvn javadoc:aggregate -PjavadocDist -Djavadoc.branding='JBoss Enterprise Application Platform 6.0.1.GA'  -Dmaven.repo.local=../local-repo-eap -s ../tools/maven/conf/settings.xml
 
, I get the following error:
 
      [ERROR] Unable to get dependency information for junit:junit:jar:4.10-redhat-1: Failed to process POM for junit:junit:jar:4.10-redhat-1: Non-resolvable parent POM for org.jboss:jboss-parent:8-redhat-1: Could not find artifact
      org.jboss.component.management:jboss-component-version-master:pom:6.0.0-redhat-1 in eap6-mirror-setting (http://download.lab.bos.redhat.com/brewroot/repos/jb-eap-6-rhel-6-build/latest/maven/)

The cause is that something uses wrong jUnit - 4.10-redhat-1 instead of redhat-2. 

http://download.lab.bos.redhat.com/brewroot/repos/jb-eap-6-rhel-6-build/latest/maven/junit/junit/4.10-redhat-1/junit-4.10-redhat-1.pom

Comment 1 Ondřej Žižka 2012-09-10 13:22:00 UTC
Link: Added: This issue is a dependency of JBPAPP-9838


Comment 3 Ondřej Žižka 2012-09-10 13:54:51 UTC
Just found it, too.
In that case, it's caused by one of these:

./local-repo-eap/joda-time/joda-time/1.6.2-redhat-2/joda-time-1.6.2-redhat-2.pom:
           <version>4.10-redhat-1</version>

./local-repo-eap/org/jboss/logmanager/log4j-jboss-logmanager/1.0.1.Final-redhat-1/log4j-jboss-logmanager-1.0.1.Final-redhat-1.pom:      
           <version>4.10-redhat-1</version>

./local-repo-eap/org/jboss/component/management/jboss-component-version-master/6.0.0-redhat-2/jboss-component-version-master-6.0.0-redhat-2.pom:
           <version.junit>[4.10-redhat-1,4.10-redhat-2]</version.junit>

Comment 4 Vladimir Dosoudil 2012-09-10 14:13:33 UTC
It obviously seems there are:

* bad POM of joda-time 1.6.2-redhat-2
** maintainer didn't remove versions from dependencies (EAP BOM is not used)
* missing correct "unsigned rebuild" of log4j-jboss-logmanager
** maintainer used bad version string for unsigned rebuild
** and didn't remove versions from dependencies (EAP BOM is not used)
* EAP BOM 6.0.0-redhat-2 is temporary and unstable, it mustn't be used in any well-productized component of EAP 6.0.1

Comment 5 Ondřej Žižka 2012-09-10 22:07:38 UTC
Link: Added: This issue depends JBPAPP-9872


Comment 6 Ondřej Žižka 2012-09-10 22:07:38 UTC
Link: Added: This issue depends JBPAPP-9871


Comment 7 Ondřej Žižka 2012-09-10 22:08:18 UTC
Reopening, let's close when the dependency issues are closed.

Comment 8 Ondřej Žižka 2012-10-24 13:42:38 UTC
This is gone, probably was fixed.

Comment 9 Anne-Louise Tangring 2012-11-13 20:55:42 UTC
Docs QE Status: Removed: NEW 


Comment 10 Rostislav Svoboda 2012-11-19 13:30:20 UTC
Verified on EAP 6.0.1 ER3

[rsvoboda@steve 601ER3]$ grep 4.10-redhat-1 . -R
[rsvoboda@steve 601ER3]$