| Summary: | provide stable maven repo url for EAP 5.1.1 artifacts | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Aleksandar Kostadinov <akostadinov> |
| Component: | EAP | Assignee: | Aleksandar Kostadinov <akostadinov> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.2.0.ER4 | CC: | akostadinov, dpalmer, mvecera |
| Target Milestone: | --- | Keywords: | TestBlocker |
| Target Release: | 5.2.0 GA, 5.2.0.ER4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-3429 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-07 13:53:11 UTC | Type: | Task |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Aleksandar Kostadinov
2011-10-01 05:25:08 UTC
Link: Added: This issue depends JBPAPP-1935 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. 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. 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/ Writer: Added: dlesage 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) 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. I have filed [engineering.redhat.com #125230]. 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. |