Bug 745874 (EDG-85) - new mead repository needs to be added to EDG pom.xml
Summary: new mead repository needs to be added to EDG pom.xml
Keywords:
Status: CLOSED NEXTRELEASE
Alias: EDG-85
Product: JBoss Data Grid 5
Classification: JBoss
Component: Infinispan
Version: EAP 5.1.0 EDG TP
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: EAP 5.1.0 EDG TP
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/EDG-85
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-29 14:55 UTC by Michal Linhard
Modified: 2014-03-17 04:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-28 15:20:40 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EDG-85 0 Major Closed new mead repository needs to be added to EDG pom.xml 2013-08-30 14:50:22 UTC

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


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