Re: The URL appending issue and Maven Central

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: The URL appending issue and Maven Central

Hervé BOUTEMY
yes, if someone at Apache wants to use the new attributes in an Apache
release, Apache Nexus Repository Manager has to be upgraded like OSSRH was

Regards,

Hervé

Le lundi 26 août 2019, 17:10:56 CEST Mirko Friedenhagen a écrit :

> Hello,
>
> just a question: according to NEXUS-19912[1] I see the issue was fixed in
> release 2.14.4 of Nexus. Looking at https://repository.apache.org/
> <https://repository.apache.org/> 2.14.12-0 is still used. Should INFRA
> update this as well to avoid the same issue?
>
>
> Best Regards
> Mirko
>
> [1] https://issues.sonatype.org/browse/NEXUS-19912
>
> > Am 09.07.2019 um 08:16 schrieb Hervé BOUTEMY <[hidden email]>:
> >
> > you have created MVNCENTRAL-4841 [1] issue 2 months ago: this is where to
> > ping for updates
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://issues.sonatype.org/browse/MVNCENTRAL-4841
> > <https://issues.sonatype.org/browse/MVNCENTRAL-4841>>
> > Le lundi 8 juillet 2019, 12:23:57 CEST Mark Raynsford a écrit :
> >> Hello!
> >>
> >> This is still a problem:
> >>  https://issues.apache.org/jira/browse/MNG-5951
> >>  https://issues.apache.org/jira/browse/MNG-6059
> >>
> >> The problem isn't that the behaviour hasn't been fixed, but instead
> >> that the POM files that use the new attributes can't be deployed to
> >> Maven Central. I reported the issue to Sonatype, but it's been eight
> >> months [0] and nothing has been done about it. I think it might be case
> >> of the Sonatype people waiting to see what the Maven people will do, and
> >> the Maven people waiting to see what the Sonatype people will do. :)
> >>
> >> I wonder if, instead, we could just turn off this URL appending
> >> behaviour with a property? Ideally the property would be specified in
> >> the POM file and the model would stay entirely backwards compatible.
> >> If you don't set the property to true, you get the old url-mangling
> >> behaviour.
> >>
> >> <pom>
> >>
> >>  <properties>
> >>
> >> <maven.please.leave.my.urls.alone>true</maven.please.leave.my.urls.alone>
> >> </properties>
> >>
> >>  ...
> >>
> >> I'm *still* in the situation where I can either add the attributes to
> >> my projects and get correct metadata but be unable to publish to
> >> Central, or avoid using the attributes and get wildly incorrect
> >> metadata but be able to publish to Central. Both choices are
> >> pretty much unacceptable. Free to publish garbage, or prevented from
> >> publishing non-garbage!
> >>
> >> I'd like to see some movement on this... What do I need to do to get
> >> this sorted out?
> >>
> >> [0] https://blog.io7m.com/2018/11/23/lurking-between-releases.xhtml
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > <mailto:[hidden email]> For additional commands,
> > e-mail: [hidden email] <mailto:[hidden email]>





---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]