[
https://issues.apache.org/jira/browse/OPENEJB-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Gumbrecht resolved OPENEJB-1918.
-------------------------------------
Resolution: Fixed
Fix Version/s: (trunk/openejb)
Searched for and checked in all pom.xml - Appears to be resolved so closing.
> Build relies on <repositories> and <pluginRepositories>
> -------------------------------------------------------
>
> Key: OPENEJB-1918
> URL: https://issues.apache.org/jira/browse/OPENEJB-1918
> Project: OpenEJB
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.1
> Reporter: Stephen Connolly
> Assignee: Stephen Connolly
> Priority: Minor
> Labels: maven, stephenc-to-fix
> Fix For: (trunk/openejb)
>
>
> There are a number of pom.xml's that reference repositories other than
> http://repository.apache.org/snapshots
> And even those that reference the snapshots repository do not do so correctly
> <url>http://snapshots.repository.codehaus.org/</url>
> is referenced as a snapshot repo correctly, so can probably stay, but I need
> to look into optimizing its usage
> This will most probably include trying to get
> <repository>
> <id>eclipselink-repo</id>
> <name>EclipseLink Repository</name>
>
> <url>http://www.eclipse.org/downloads/download.php?r=1&nf=1&file=/rt/eclipselink/maven.repo</url>
> </repository>
> into central
> and figuring out what to do about
> <repository>
> <id>ctp-consulting-m2-snapshot</id>
> <name>Ctp Consulting Snapshot Repository</name>
>
> <url>https://repository-ctpconsulting.forge.cloudbees.com/snapshot/</url>
> </repository>
> (note that looks to be a snapshot repo but is not referenced correctly for a
> snapshot repo)
> <repository>
> <id>tomcat-m2-repo</id>
> <name>Tomcat Dev Repository</name>
> <url>http://tomcat.apache.org/dev/dist/m2-repository/</url>
> </repository>
> is a more interesting problem
> as is
> <url>https://repository.jboss.org/nexus/content/groups/public/</url>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
