Bug 1317546

Summary:	Many B*MS artifacts' pom.xml contained in GA maven repository still pointing to techpreview repository URL
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Musharraf Hussain <mhussain>
Component:	Maven Repository	Assignee:	Ryan Zhang <rzhang>
Status:	CLOSED EOL	QA Contact:	Marek Winkler <mwinkler>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.2.0	CC:	anstephe, lpetrovi, pkocandr, rrajasek, rzhang
Target Milestone:	CR1
Target Release:	6.3.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-27 19:05:33 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 Musharraf Hussain 2016-03-14 14:01:11 UTC

Description of problem:
- It has been observed that there are many BPMS/BRMS artifacts' pom.xml file available in the official GA maven repository still points to the "https://maven.repository.redhat.com/techpreview/all/" repository URL . It causes a lot of confusion in customer's minds as well as issues. Can we fix this problem for all such artifacts? Here are some of those artifacts' pom for reference.

[1] https://maven.repository.redhat.com/nexus/content/groups/product-ga/org/kie/kie-parent-metadata/6.3.0.Final-redhat-7/kie-parent-metadata-6.3.0.Final-redhat-7.pom
[2] https://maven.repository.redhat.com/nexus/content/groups/product-ga/org/kie/kie-api-parent/6.3.0.Final-redhat-7/kie-api-parent-6.3.0.Final-redhat-7.pom
[3] https://maven.repository.redhat.com/nexus/content/groups/product-ga/org/jbpm/jbpm/6.3.0.Final-redhat-7/jbpm-6.3.0.Final-redhat-7.pom

Version-Release number of selected component (if applicable):
- 6.3.0-Final-redhat-7

How reproducible:
- Always

Steps to Reproduce:
1. Please see description above
2.
3.

Actual results:
- pom.xml point to techpreview maven repository

Expected results:
- pom.xml point to GA maven repository

Additional info:
- Nothing

Comment 2 Petr Kočandrle 2016-03-14 16:42:00 UTC

Unfortunately there is no way how to fix this. The artifacts has been released already and we cannot modify them. The only thing we can fix is modify the url for future releases if it has not been done yet. Although I was surprised that the repositories tag is in the poms. This is exactly the case why we recommend usage of settings.xml instead of repositories hardcoded in poms. The only case I know about where it makes sense is in quickstarts/examples artifacts where it can lower the barrier for newcomers.

Comment 3 Musharraf Hussain 2016-03-15 06:08:14 UTC

Yes, it was surprising for me too to see the <repository> used in the pom.xml files as it creates unnecessary complexities and dependencies in customer cases where they can't afford to connect to public maven artifact repositories and they rely on off-line artifacts only. If such tags can be totally removed then it would be great indeed. In future releases as of now :)

Thanks for looking into this matter.

Comment 6 Ryan Zhang 2016-04-20 05:49:24 UTC

This already been fixed in 6.3 released.
The redhat maven repository url has been fixed.
eg:
http://download.englab.bne.redhat.com//devel/candidates/BRMS/BRMS-6.3.0.ER3/maven-repository/maven-repository/org/kie/kie-parent-metadata/6.4.0.Final-redhat-1/kie-parent-metadata-6.4.0.Final-redhat-1.pom

Comment 9 Marek Winkler 2016-04-29 10:25:08 UTC

Verified in BRMS 6.3.0 CR1, the <repositories> tag is not defined in product pom.xml at all [1]. 

I have also searched Maven repository content for "<repositories>" and it was not found in any BxMS product artifact (only in a few third-party artifacts). 

[1] http://download.englab.bne.redhat.com//devel/candidates/BRMS/BRMS-6.3.0.CR1/maven-repository/maven-repository/org/kie/kie-parent-metadata/6.4.0.Final-redhat-2/kie-parent-metadata-6.4.0.Final-redhat-2.pom