[
https://jira.jboss.org/jira/browse/JBBUILD-601?page=com.atlassian.jira.pl...
]
Manik Surtani commented on JBBUILD-601:
---------------------------------------
Further proxies needed (asap)
<repository>
<id>berkeleydb-je.repository</id>
<
url>http://download.oracle.com/maven/</url>
</repository>
<repository>
<id>jclouds</id>
<
url>http://jclouds.googlecode.com/svn/repo</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>jclouds-snapshots</id>
<
url>http://jclouds.rimuhosting.com/maven2/snapshots</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
<repository>
<id>spy</id>
<name>Spy Repository</name>
<layout>default</layout>
<
url>http://bleu.west.spy.net/~dustin/m2repo/</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<!-- needed for XSOM -->
<repository>
<id>download.java.net</id>
<
url>http://download.java.net/maven/2</url>
</repository>
Add a Proxy in Nexus to point to
http://scala-tools.org/repo-releases
---------------------------------------------------------------------
Key: JBBUILD-601
URL:
https://jira.jboss.org/jira/browse/JBBUILD-601
Project: JBoss Build System
Issue Type: Feature Request
Components: Artifact Repositories
Reporter: Manik Surtani
Priority: Critical
This is currently a problem since my project POM adds
http://scala-tools.org/repo-releases as a <repository> but the POM validation in
Nexus won't allow this tag.
Marking this as critical as I have a release due in a week and won't be able to
release unless this is resolved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira