Bug 745874 (EDG-85)

Summary: new mead repository needs to be added to EDG pom.xml
Product: [JBoss] JBoss Data Grid 5 Reporter: Michal Linhard <mlinhard>
Component: InfinispanAssignee: Default User <jbpapp-maint>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: EAP 5.1.0 EDG TPCC: mlinhard, nobody
Target Milestone: ---   
Target Release: EAP 5.1.0 EDG TP   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/EDG-85
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-28 15:20:40 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:

Description Michal Linhard 2011-03-29 14:55:49 UTC 
project_key: EDG

recently EAP build switched to use new mead repository:

(from http://anonsvn.jboss.org/repos/jbossas/branches/JBPAPP_5_1/pom.xml)
{code}
<repositories>
    <repository>
      <id>mead-repository.redhat.com</id>
      <name>JBoss Production Releases MEAD Repository</name>
      <url>http://download.lab.bos.redhat.com/brewroot/repos/jb-eap-5-rhel-6-build/latest/maven2</url>
      <releases>
        <enabled>true</enabled>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
    </repository>
    <repository>
      <id>prod-repository.jboss.org</id>
      <name>JBoss Production Releases Repository</name>
      <url>http://repository.jboss.org/maven2-brew</url>
      <releases>
        <enabled>false</enabled>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
    </repository>
    <repository>
      <id>nexus.jboss.org</id>
      <name>JBoss Nexus Repository</name>
      <url>https://repository.jboss.org/nexus/content/groups/public/</url>
      <releases>
        <enabled>true</enabled>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
    </repository>
  </repositories>
{code}

we're still using an old one
(from http://anonsvn.jboss.org/repos/jbossas/branches/JBPAPP_5_1_datagrid/pom.xml)
{code}
  <repositories>
    <repository>
      <id>prod-repository.jboss.org</id>
      <name>JBoss Production Releases Repository</name>
      <url>http://repository.jboss.org/maven2-brew</url>
      <releases>
        <enabled>true</enabled>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
    </repository>
    <repository>
      <id>nexus.jboss.org</id>
      <name>JBoss Nexus Repository</name>
      <url>https://repository.jboss.org/nexus/content/groups/public/</url>
      <releases>
        <enabled>true</enabled>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
    </repository>
  </repositories>
{code}

and this might be cause of our CI job failing:
http://hudson.qa.jboss.com/hudson/view/EDG/job/JBoss-EAP-5.1.x-datagrid/

I'll try to sync the repo config with the new settings in JBPAPP_5_1 branch and see if it helps.
Comment 1 Michal Linhard 2011-03-30 09:46:22 UTC 
We will probably need to leave the old repo (http://repository.jboss.org/maven2-brew) enabled