ALL artifacts in repository https://repository.jboss.org/nexus/content/repositories/public-jboss return 404?

[veitg]

Hi.

Since this morning, deprecated repos return 403. So we wanted to switch to:

https://repository.jboss.org/nexus/content/repositories/public-jboss/

Since this should be the current one, right?

Maven still complains about missing jboss-javaee. So I took a look via browser. Looked okay. Didn't understand why

maven complained. But as I clicked on a jar or pom, it returned 404! So structure seems to be ok, but as soon as one tries to get

a file, 404 is returned. Tried randomly other files, with the same effect. Also with /public.

Is that expected behavior?

[veitg]

Ok, after some hours of trial and error replacing the old repository definition:

<repository>

    <id>jboss-public-repository-group</id>

    <name>JBoss - Public JBoss Repository Group</name>

    <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>

    <layout>default</layout>

</repository>

with:

<repository>

    <id>repository.jboss.org</id>

    <name>JBoss - Releases Repository</name>

    <url>https://repository.jboss.org/nexus/content/repositories/releases</url>

    <layout>default</layout>

</repository>

<repository>

    <id>thirdparty.jboss.org</id>

    <name>JBoss - Third Party Repository</name>

    <url>https://repository.jboss.org/nexus/content/repositories/thirdparty-releases</url>

    <layout>default</layout>

</repository>

<repository>

    <id>deprecated.jboss.org</id>

    <name>JBoss - Deprecated Repository</name>

    <url>https://repository.jboss.org/nexus/content/repositories/deprecated/</url>

    <layout>default</layout>

</repository>

did the trick. Is that somewhere mentioned? Maybe a good idea to put that somewhere to avoid that someone has to go

through that again.

[pgier]

I think this is a bug in Nexus.  When using a repository group (instead of a hosted repository), you have to put "groups" in the path instead of "repositories".

So this URL is incorrect:

https://repository.jboss.org/nexus/content/repositories/public-jboss/

It should be:

https://repository.jboss.org/nexus/content/groups/public-jboss/

The bug in Nexus is that the first URL appears to work until you try to actually download any files as you found out.

The correct URL is documented on the getting started wiki page:

http://community.jboss.org/wiki/MavenGettingStarted-Users

I created a Nexus jira for this:

https://issues.sonatype.org/browse/NEXUS-4654

[veitg]

Thanks. Meanwhile I found out, that a combination of

https://repository.jboss.org/nexus/content/groups/public-jboss/

with

https://repository.jboss.org/nexus/content/repositories/deprecated/

Seems to work as well.

[pgier]

Veit Guna wrote:

https://repository.jboss.org/nexus/content/repositories/deprecated/

Seems to work as well.

Please try to avoid using the deprecated repo.  The stuff was deprecated for a reason

There is also a wiki page which can help you track down the correct dependencies to use in your build:

http://community.jboss.org/wiki/JBossDeprecatedRepository

[veitg]

Of course. But it's not me requiring the dependencies from deprecated. It's some of the jboss jars or their deps

as it seems. E.g. apache-xerces isn't found when specifying the jboss public only.