Re: [jaxb-dev] Maven Central has bad meta data

[Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>]

Hi,

On 4/9/20 9:58 AM, Stephen Coy (eclipse) wrote:
> Hi Lonnie,
>
> I was about to say that we have been using 2.4.0-b180830.0438 with out 
> any trouble, but I see that the metadata was updated in the last 48 
> hours or less so our repo manager has not been back to visit it just yet.

we're seeing this kind of issues from time to time after deploying new 
version in different projects. The only solution for this kind of 
problems is to file a bug at Sonatype Jira against Maven Central to let 
them know about the problem and they will fix it by regenerating some 
metadata. The bug has been already filed and now it's their turn.

thanks,
--lukas

> Cheers,
>
> Steve C
>
> > On 9 Apr 2020, at 12:31 am, Lonnie Souder <lonnie@xxxxxxxxxxxxxxxx 
> > <mailto:lonnie@xxxxxxxxxxxxxxxx>> wrote:
> >
> > Hello mailing list,
> > All of our build broke this morning.  We think it is from broken metadata.
> > We use version 2.3.1 of the jaxb-runtime.
> > At our workplace there is a local artifact server however because of 
> > covid-19 we are all
> > working remotely making it a bit more challenging to deal with.
> >
> > Please get this to someone with power to fix  the issue.
> >
> >
> >
> > https://github.com/eclipse-ee4j/jaxb-ri/issues/1419
> >
> > All of our maven builds using 2.3.1 are broken.
> > Looks like someone pushed bad meta data to maven central.
> > https://repo1.maven.org/maven2/org/glassfish/jaxb/jaxb-runtime/maven-metadata.xml
> >
> > It only includes the 3.0.0-M version.
> >
> >
> >
> > _______________________________________________
> > jaxb-dev mailing list
> > jaxb-dev@xxxxxxxxxxx <mailto:jaxb-dev@xxxxxxxxxxx>
> > To unsubscribe from this list, visit 
> > https://www.eclipse.org/mailman/listinfo/jaxb-dev
>
>
> _______________________________________________
> jaxb-dev mailing list
> jaxb-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jaxb-dev