-
1. Re: JBoss Nexus outdage?
Hum.. never mind. I see that the following works:
https://repository.jboss.org/nexus/content/groups/public-jboss
Is there reason I can't use https://repository.jboss.org/nexus/content/groups/public/ ? I thought this is a "catchall" url for all other sub-repo. No? (It used to work for me before.)
-
2. Re: JBoss Nexus outdage?
The "public" group include proxy repositories such as the java.net repo. The "public-jboss" group will give you only stuff that is controlled by the JBoss community. Both of these groups should be working. There's some more information about how the repo is set up in the wiki: http://community.jboss.org/wiki/MavenRepository
-
3. Re: JBoss Nexus outdage?
The JBoss Nexus (still?) seems to be unavailable - if I request any of the Nexus content URLs I get an empty HTML document as reply. It also does not work with Maven. Is there a known problem or do I have some configuration issues?
-
4. Re: JBoss Nexus outdage?
The JBoss Nexus instance is working ok. Our infrastructure team had to disable file/directory browsing because it was causing too much load on the server. But it should still work fine for your builds. If it's not working for your builds, you can submit a JBBUILD jira issue (https://issues.jboss.org/browse/JBBUILD) along with some info about the error you are seeing.