Re: [VOTE] Release Maven Project Info Reports Plugin version 3.0.1

[Gabriel Belingueres]

Hi:

Regarding the exception, there were several cases I checked:

Case 1:


  

  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.0.1
  


org.eclipse.m2e

  

  


it was not finding the very same plugin I was testing:
"org.apache.maven.project.ProjectBuildingException: Error resolving project
artifact: Failure to find
org.apache.maven.plugins:maven-project-info-reports-plugin:pom:3.0.1 in
https://repo.maven.apache.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central has
elapsed or updates are forced for project
org.apache.maven.plugins:maven-project-info-reports-plugin:pom:3.0.1"

The reason for this exception is that it could not find it when declared in
the pluginManagement section, because it tries to get it as an artifact and
it was not found. Adding the same plugin staging repo like this solved the
exception:
  

  same-staged-repo
  https://repository.apache.org/content/repositories/maven-1528


  

I think this condition should dissapear as soon as the plugin is deployed
to Central repo?

Case 2:
Executing again with the artifact repo added caused this exception:
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure
to find org.eclipse.m2e:lifecycle-mapping:pom:1.0.0 in http:// was
cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced

which is what is expected as the 'mvn site' execution does not set the
parameters in the plugin configuration section of plugins.

Case 3:
Leave the pluginManagement section but configure it in the reporting
section:

  

  org.apache.maven.plugins
  maven-project-info-reports-plugin
  3.0.1

  

  


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  


org.eclipse.m2e

  


  

Works OK as long as the artifact repository is kept.

Case 4:
If I delete the artifact repository, to avoid the exception "...Failure to
find
org.apache.maven.plugins:maven-project-info-reports-plugin:pom:3.0.1..." I
excluded the plugin in the configuration (showing that the added
functionality works for the plugin itself):
  


  org.apache.maven.plugins
  maven-project-info-reports-plugin
  


org.eclipse.m2e

org.apache.maven.plugins:maven-project-info-reports-plugin

  


  

HTH
Gabriel

El lun., 26 de ago. de 2019 a la(s) 09:59, Tibor Digana (
tibordig...@apache.org) escribió:

> I was waiting this this issue. Now it is clear for me too.
> So we are missing this commit, right? It's worth to complete the PR#7 and
> restart the vote.
>
> Gabriel, why the exception with plugin version 3.0.1 appears on your box?
> T
>
> On Mon, Aug 26, 2019 at 2:49 PM Gabriel Belingueres  >
> wrote:
>
> > Created https://issues.apache.org/jira/browse/MPIR-384
> >
> > Kind regards,
> > Gabriel
> >
> > El lun., 26 de ago. de 2019 a la(s) 05:21, Michael Osipov (
> > micha...@apache.org) escribió:
> >
> > > Am 2019-08-26 um 04:14 schrieb Gabriel Belingueres:
> > > > Hi:
> > > >
> > > > In the light of what Michael clarified, and after some doc reading
> [1],
> > > > quoting the following about 'mvn site':
> > > > "It uses *only* the parameters defined in the  element
> > of
> > > > each reporting Plugin specified in the  element, i.e. site
> > > > always *ignores* the parameters defined in the 
> element
> > of
> > > > each plugin specified in ."
> > > >
> > > > After testing with the plugin configuration in the 
> section,
> > > it
> > > > worked OK. Why it does not apply the reporting configuration when the
> > > > plugin is declared and configured in both the pluginManagement and
> > > > repoorting sections is another matter.
> > > >
> > > > I created a gist with the log files as it seems the mailing does not
> > > allow
> > > > attachments. Please see [2], but it seems less useful now.
> > > >
> > > > Regarding the missing commit, it was an improvement over the first
> > commit
> > > > (which already had the IT in place). The feature is already there and
> > > > working. I have no problem to  raise a new issue for the next
> release.
> > >
> > > Please do so.
> > >
> > > @Tibor. Do you still insist on -1?
> > >
> > > @all if Tibor reverts his one, I still need another binding vote.
> > >
> >
>

Re: The URL appending issue and Maven Central

[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: [VOTE] Release Maven Project Info Reports Plugin version 3.0.1

[Tibor Digana]

I was waiting this this issue. Now it is clear for me too.
So we are missing this commit, right? It's worth to complete the PR#7 and
restart the vote.

Gabriel, why the exception with plugin version 3.0.1 appears on your box?
T

On Mon, Aug 26, 2019 at 2:49 PM Gabriel Belingueres 
wrote:

> Created https://issues.apache.org/jira/browse/MPIR-384
>
> Kind regards,
> Gabriel
>
> El lun., 26 de ago. de 2019 a la(s) 05:21, Michael Osipov (
> micha...@apache.org) escribió:
>
> > Am 2019-08-26 um 04:14 schrieb Gabriel Belingueres:
> > > Hi:
> > >
> > > In the light of what Michael clarified, and after some doc reading [1],
> > > quoting the following about 'mvn site':
> > > "It uses *only* the parameters defined in the  element
> of
> > > each reporting Plugin specified in the  element, i.e. site
> > > always *ignores* the parameters defined in the  element
> of
> > > each plugin specified in ."
> > >
> > > After testing with the plugin configuration in the  section,
> > it
> > > worked OK. Why it does not apply the reporting configuration when the
> > > plugin is declared and configured in both the pluginManagement and
> > > repoorting sections is another matter.
> > >
> > > I created a gist with the log files as it seems the mailing does not
> > allow
> > > attachments. Please see [2], but it seems less useful now.
> > >
> > > Regarding the missing commit, it was an improvement over the first
> commit
> > > (which already had the IT in place). The feature is already there and
> > > working. I have no problem to  raise a new issue for the next release.
> >
> > Please do so.
> >
> > @Tibor. Do you still insist on -1?
> >
> > @all if Tibor reverts his one, I still need another binding vote.
> >
>

Re: [VOTE] Release Maven Project Info Reports Plugin version 3.0.1

[Gabriel Belingueres]

Created https://issues.apache.org/jira/browse/MPIR-384

Kind regards,
Gabriel

El lun., 26 de ago. de 2019 a la(s) 05:21, Michael Osipov (
micha...@apache.org) escribió:

> Am 2019-08-26 um 04:14 schrieb Gabriel Belingueres:
> > Hi:
> >
> > In the light of what Michael clarified, and after some doc reading [1],
> > quoting the following about 'mvn site':
> > "It uses *only* the parameters defined in the  element of
> > each reporting Plugin specified in the  element, i.e. site
> > always *ignores* the parameters defined in the  element of
> > each plugin specified in ."
> >
> > After testing with the plugin configuration in the  section,
> it
> > worked OK. Why it does not apply the reporting configuration when the
> > plugin is declared and configured in both the pluginManagement and
> > repoorting sections is another matter.
> >
> > I created a gist with the log files as it seems the mailing does not
> allow
> > attachments. Please see [2], but it seems less useful now.
> >
> > Regarding the missing commit, it was an improvement over the first commit
> > (which already had the IT in place). The feature is already there and
> > working. I have no problem to  raise a new issue for the next release.
>
> Please do so.
>
> @Tibor. Do you still insist on -1?
>
> @all if Tibor reverts his one, I still need another binding vote.
>

Re: [VOTE] Release Maven Project Info Reports Plugin version 3.0.1

[Michael Osipov]

Am 2019-08-26 um 04:14 schrieb Gabriel Belingueres:

Hi:

In the light of what Michael clarified, and after some doc reading [1],
quoting the following about 'mvn site':
"It uses *only* the parameters defined in the  element of
each reporting Plugin specified in the  element, i.e. site
always *ignores* the parameters defined in the  element of
each plugin specified in ."

After testing with the plugin configuration in the  section, it
worked OK. Why it does not apply the reporting configuration when the
plugin is declared and configured in both the pluginManagement and
repoorting sections is another matter.

I created a gist with the log files as it seems the mailing does not allow
attachments. Please see [2], but it seems less useful now.

Regarding the missing commit, it was an improvement over the first commit
(which already had the IT in place). The feature is already there and
working. I have no problem to  raise a new issue for the next release.


Please do so.

@Tibor. Do you still insist on -1?

@all if Tibor reverts his one, I still need another binding vote.

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