Bug 916573 - Duplicated artifacts in maven repo for EAP 610 ERx
Summary: Duplicated artifacts in maven repo for EAP 610 ERx
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Maven Repository
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: EAP 6.1.0
Assignee: Paul Gier
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-28 11:27 UTC by Rostislav Svoboda
Modified: 2013-09-09 15:58 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-19 12:05:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rostislav Svoboda 2013-02-28 11:27:30 UTC
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Repository/job/eap-60-repository-maven-check-unique-artifactId/30/artifact/test-output.txt

hibernate-commons-annotations				      <
jboss-component-management				      <
jboss-component-version-master				      <
jboss-dependency-management-all				      <
jboss-dependency-management-build			      <
jboss-dependency-management-eap				      <
jboss-logging-processor					      <
jboss-parent						      <
jboss-project-dependency-management			      <
jboss-project-dependency-relocations			      <


jsf-impl is expected

Comment 1 Rostislav Svoboda 2013-03-08 08:44:07 UTC
EAP 6.1.0 ER2

hibernate-commons-annotations				      <
jboss-component-management				      <
jboss-component-version-master				      <
jboss-dependency-management-all				      <
jboss-dependency-management-build			      <
jboss-dependency-management-eap				      <
jboss-parent						      <
jboss-project-dependency-management			      <
jboss-project-dependency-relocations			      <

Comparing to ER1, only jboss-logging-processor was fixed

Comment 2 Paul Gier 2013-03-18 14:15:24 UTC
The duplicate hibernate-commons-annotations has been removed from the current builds.

The other duplicates (eap bom project and jboss-parent) are expected.  The reason for this is because we will carry over a lot of the 6.0.1 content, anything that did not need to be rebuilt.  The 6.0.1 poms still depend on the older jboss-parent and eap bom, and without them, there would be a lot of invalid pom errors.

Can those be excluded from the test?  Also maybe this test can be included in our hand off smoke tests?

Comment 3 Rostislav Svoboda 2013-03-19 09:14:43 UTC
Script changed to contain info about expected duplications.

> included in our hand off smoke tests

Just clone the eap-60-repository-maven-check-unique-artifactId job and include it in hand-off trigger, it needs just parameters REPO_ZIP, REPO_DIR and REPORT_DIR which should be already set by the trigger.

Comment 4 Rostislav Svoboda 2013-03-19 09:30:54 UTC
Script changed to exclude expected duplications from report

Comment 5 Rostislav Svoboda 2013-03-20 13:39:13 UTC
EAP 6.1.0 ER3 maven repo zip contains new duplications:

jboss-servlet-api_3.0_spec				      <
jbossws-parent						      <
jcl-over-slf4j						      <
relaxngDatatype						      <
slf4j-api						      <
slf4j-parent						      <


Details in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Repository/job/eap-60-repository-maven-check-unique-artifactId/32/artifact/test-output.txt

Comment 7 Rostislav Svoboda 2013-04-19 12:05:30 UTC
Closing as this won't be fixed in EAP 6.1.x. This would need correct rebuild of all artifacts for release and prod team doesn't have capacity to perform such time and HW consuming operation.


Note You need to log in before you can comment on or make changes to this bug.