Re: The URL appending issue and Maven Central

2019-08-27 Thread 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/
>  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 :
> > 
> > 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
> > > 
> > 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.
> >> 
> >> 
> >> 
> >>  
> >> 
> >> true
> >> 
> >> 
> >>  ...
> >> 
> >> 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: dev-unsubscr...@maven.apache.org
> >  For additional commands,
> > e-mail: dev-h...@maven.apache.org 





-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: The URL appending issue and Maven Central

2019-08-26 Thread Mirko Friedenhagen
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/  
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 :
> 
> 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 
> 
> 
> 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.
>> 
>> 
>>  
>> 
>> true
>> 
>>  ...
>> 
>> 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: dev-unsubscr...@maven.apache.org 
> 
> For additional commands, e-mail: dev-h...@maven.apache.org 
> 


Re: The URL appending issue and Maven Central

2019-07-09 Thread Mark Raynsford
On 2019-07-09T08:16:14 +0200
Hervé BOUTEMY  wrote:

> you have created MVNCENTRAL-4841 [1] issue 2 months ago: this is where to 
> ping 
> for updates

Ah, thanks! Didn't know about that one. I'll comment on it and link to
my old ticket.

-- 
Mark Raynsford | http://www.io7m.com



pgp7VwvITMR2_.pgp
Description: OpenPGP digital signature


Re: The URL appending issue and Maven Central

2019-07-09 Thread Hervé BOUTEMY
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

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.
> 
>  
>   
>
> true
> 
>   ...
> 
> 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: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: The URL appending issue and Maven Central

2019-07-08 Thread Mark Raynsford
On 2019-07-08T19:46:38 +0200
"Robert Scholte"  wrote:

> Hi Mark,
> 
> I'm working on some improvements which might be related to this.
> My main question: is the pom containing the special attributes part of the  
> Maven Multimodule project?

Not quite sure how to interpret this one. In my case, I'd specify those
attributes on a distant ancestor POM and then inherit from that POM in
the root POMs of many of separate multi-module projects.

> If so, I should be able to calculate the right URL based on the local  
> folder structure instead of pom inheritence via parent, right?

I think calculating is the whole problem: I actually specifically don't
want any calculation going on. I've specified the URIs myself and I'd
prefer it if Maven both inherited the values directly from parents, and
left the URL values alone without any appending or other mangling. :)

-- 
Mark Raynsford | http://www.io7m.com



pgpN_el3zCG14.pgp
Description: OpenPGP digital signature


Re: The URL appending issue and Maven Central

2019-07-08 Thread Robert Scholte

Hi Mark,

I'm working on some improvements which might be related to this.
My main question: is the pom containing the special attributes part of the  
Maven Multimodule project?
If so, I should be able to calculate the right URL based on the local  
folder structure instead of pom inheritence via parent, right?


thanks,
Robert

On Mon, 08 Jul 2019 12:23:57 +0200, Mark Raynsford  
 wrote:



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.

 
  
true
  
  ...

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: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: The URL appending issue and Maven Central

2019-07-08 Thread Mark Raynsford
On 2019-07-08T11:23:57 +0100
Mark Raynsford  wrote:
>
> I'd like to see some movement on this... What do I need to do to get
> this sorted out?

To be clear, I'm offering my time and resources here. I'm not just
demanding that other people do work on my behalf.

-- 
Mark Raynsford | http://www.io7m.com



pgp6gdYo5jfs3.pgp
Description: OpenPGP digital signature


Re: The URL appending issue and Maven Central

2019-07-08 Thread Mark Raynsford
On 2019-07-08T11:34:02 +0100
Mark Raynsford  wrote:
>
> automatically propagate to all ancestors
 ^

Clearly I meant *descendants*. Sorry!

-- 
Mark Raynsford | http://www.io7m.com



pgpNW3WO0T2GH.pgp
Description: OpenPGP digital signature


Re: The URL appending issue and Maven Central

2019-07-08 Thread Mark Raynsford
On 2019-07-08T11:23:57 +0100
Mark Raynsford  wrote:
>
> 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.

I forgot to point out that specifying this in a parent POM should, by
my understanding of Maven's property inheritance rules, automatically
propagate to all ancestors. This would be ideal for me given that I
have ~900 pom.xml files that would otherwise have to be updated by
hand. :)

-- 
Mark Raynsford | http://www.io7m.com



pgpwwKJvF2boX.pgp
Description: OpenPGP digital signature


The URL appending issue and Maven Central

2019-07-08 Thread Mark Raynsford
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.

 
  
true
  
  ...

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

-- 
Mark Raynsford | http://www.io7m.com


pgpHn7JBhe4zX.pgp
Description: OpenPGP digital signature