Hi again, small update, it seems this sync issue between the Maven repos is already known
and is being worked out. I will let you know once solved.
—E
On 16 Dec 2021, at 12:12, Eduardo Martins <emartins(a)redhat.com>
wrote:
Hi Wolfgang, from our side nothing changed in the release process, we (WildFly team) only
deploy artifacts to the JBoss public repo, and those are then mirrored to Central repo
automatically. I dunno if there is just a delay in the mirroring process or something
externally changed, let’s wait a few more days to see if the 26.0.0.Final BOMs, which were
released yesterday, are mirrored or not, and if that doesn’t happen then will look into
it.
—E
On Thu, 16 Dec 2021 at 12:03, Wolfgang Knauf <wolfgang.knauf(a)gmx.de
<mailto:wolfgang.knauf@gmx.de>> wrote:
Hi all,
while trying to update the archetypes to WildFly 26, I noticed that the
BOMs for Beta1 and Final are missing in maven central, e.g:
https://repo.maven.apache.org/maven2/org/wildfly/bom/wildfly-jakartaee8-w...
<
https://repo.maven.apache.org/maven2/org/wildfly/bom/wildfly-jakartaee8-w...
The JBoss repository contains them:
https://repository.jboss.org/nexus/content/groups/public/org/wildfly/bom/...
<
https://repository.jboss.org/nexus/content/groups/public/org/wildfly/bom/...
What has happened here ? Any chance to fix this? Or does the archetype
have to include the JBoss repository?
Best regards
Wolfgang
_______________________________________________
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
<mailto:wildfly-dev@lists.jboss.org>
To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
<mailto:wildfly-dev-leave@lists.jboss.org>
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s