Bug 780960 (SOA-3429) - provide stable maven repo url for EAP 5.1.1 artifacts
Summary: provide stable maven repo url for EAP 5.1.1 artifacts
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3429
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EAP
Version: 5.2.0.ER4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.2.0 GA,5.2.0.ER4
Assignee: Aleksandar Kostadinov
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-01 05:25 UTC by Aleksandar Kostadinov
Modified: 2011-10-07 13:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-07 13:53:11 UTC
Type: Task


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3429 0 Blocker Closed provide stable maven repo url for EAP 5.1.1 artifacts 2014-06-26 23:33:25 UTC

Description Aleksandar Kostadinov 2011-10-01 05:25:08 UTC
project_key: SOA

At the moment we rely on mead builds[1] to download EAP5 artifacts for running EAP 5.1.1 test suite against SOA-P. However the working build seems to have been removed because some artifacts that test suite search for are missing. For example seam booking example ear present is 2.2.4 and 2.2.5 where test suite searches for 2.2.3

So to execute the test suite we need a stable URL for the maven repo used to build the EAP version SOA-P is based on (atm 5.1.1).

I can find JBPAPP-1935, it may not be feasible to provide such repo to customers but IMHO we absolutely need such repo for internal use.

[1] http://download.lab.bos.redhat.com/brewroot/repos/jb-eap-5-rhel-6-build/latest/maven

Comment 1 Aleksandar Kostadinov 2011-10-01 05:25:29 UTC
Link: Added: This issue depends JBPAPP-1935


Comment 2 Douglas Palmer 2011-10-03 15:03:57 UTC
I don't think that this is possible with EAP 5.x.x. The EAP maven repository is a side effect of the EAP build and isn't actually used to produce EAP; as a result the repository is full of broken artefacts. The SOA-P repositories initially inherited from the EAP repositories; we abandoned this when we realised the EAP repositories were broken and wouldn't be fixed.

Comment 3 Aleksandar Kostadinov 2011-10-03 16:42:23 UTC
The EAP test suite uses this URL. Without having the repository in some usable state we cannot run EAP test suite. We don't mind having more versions in the repository than necessary or other minor problems.

Comment 4 Douglas Palmer 2011-10-04 22:29:54 UTC
The following url is for the 5.1.1 release repository and should be stable:

http://download.lab.bos.redhat.com/brewroot/repos/jb-eap-5.1.1-repo/latest/maven/

Comment 5 David Le Sage 2011-10-04 22:42:35 UTC
Writer: Added: dlesage


Comment 6 Aleksandar Kostadinov 2011-10-05 09:05:50 UTC
Hello David. Thanks for looking into this problem. But the repo you have provided is not usable. As an example, see seam [1]. You can see that only version 2.2.4 is present. But in testsuite/imports/sections/seam.xml[2] you can see that EAP build expects to find version 2.2.3.

If you have hard time generating a working repo, I have an older one archived and can pass a link to it to you so you can host it in an accessible place.

[1] http://download.lab.bos.redhat.com/brewroot/repos/jb-eap-5.1.1-repo/latest/maven/org/jboss/seam/jboss-seam/
[2] https://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-eap51/ws/work/jboss-eap-5.1-src/jboss-as/testsuite/imports/sections/seam.xml (this url may go away, look at EAP source bundle)

Comment 7 Douglas Palmer 2011-10-05 09:28:56 UTC
EAP 5.1.1 ships with Seam 2.2.4.EAP5; so there is a problem with your tests if they are looking for 2.2.3.

Comment 8 Aleksandar Kostadinov 2011-10-05 14:28:23 UTC
I have filed [engineering.redhat.com #125230].

Comment 9 Aleksandar Kostadinov 2011-10-07 13:53:10 UTC
Hello, it turned out that only the seam version is wrong in the EAP test suite. To workaround the problem I used sed in the test script.

Hopefully by next releases, EAP test suite will use the correct artifacts thus work with a correct maven repo.

It seems that we don't any modifications to the repo you have provided now.

Thank you for looking into this.


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