incorrect link on HTML site

2019-08-28 Thread Śliwińska , Ewa
Hello,

link „maven 3 compatibility notes” on 
https://maven.apache.org/guides/introduction/introduction-to-profiles.html site 
is leading to “Page not found”.
I kindly ask you to fix this.

I’m trying to learn about profiles (and debug some problem), this page looks 
like quite good place to start, but I have Maven 3, and I wonder if this should 
disturb me – I mean do they information here will be still relevant (so exactly 
what I would expect from this broken link ).

Best regards
Ewa
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.


please care and vote for Chinese people under cruel autocracy of CCP, great thanks!

2019-08-28 Thread ant_fighter
Hi all,
Sorry for disturbing you guys. Though I don't think here as a proper place to 
do this, I need your help, your vote, your holy vote, for us Chinese, for 
conscience and justice, for better world.

In the over 70 years of ruling over China, the Chinese Communist Party has done 
many horrible things humans can think of. These malicious and evil deeds 
include but are not limited to: falsifying national history, suppression of 
freedom of speech and press, money laundering in the scale of trillions, live 
organ harvesting, sexual harassment and assault to underaged females, 
slaughtering innocent citizens with counter-revolutionary excuses, etc.

In light of the recent violent actions to Hong Kongers by the People's 
Liberation Army (PLA) disguised as Hong Kong Police Force, we the people 
petition to officially recognize the Chinese Communist Party as a terrorist 
organization.

PLEASE SIGNUP and VOTE for us:
https://petitions.whitehouse.gov/petition/call-official-recognition-chinese-communist-party-terrorist-organization

Thanks again for all!

nameless, an ant fighter
2019.8.29

Re: Found Issues - Release Apache Maven Version 3.6.2

2019-08-28 Thread Enrico Olivelli
It may be due to any change regarding jsr 330 like
https://issues.apache.org/jira/plugins/servlet/mobile#issue/MNG-6686


I think it is an issue for Idea and not for us.
It would be good to have some developer from Jetbrains on this list


Enrico

Il mer 28 ago 2019, 22:23 Tibor Digana  ha scritto:

> I do not have NPE in the log.
> Guice is certainly not CDI. Moving Guice to CDI must be painful.
> One reason why PathTranslator could not be found is that there are several
> bean instances of the same interface.
> Second problem might go with the Guice/CDI.
> See this inheritance:
>
> @Named
> @Singleton
> public class DefaultPathTranslator
> implements PathTranslator
> {
>
> public interface PathTranslator
> {
>
>
>
> On Wed, Aug 28, 2019 at 10:04 PM Filipe Sousa  wrote:
>
>> Hi,
>>
>> Not sure if it’s the same bug I commented in
>> https://issues.apache.org/jira/browse/MNG-6638?focusedCommentId=16852351=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16852351
>>
>> I reported to Jetbrains https://youtrack.jetbrains.com/issue/IDEA-215315
>>  and is supposed to be
>> fixed in 2019.3
>>
>> > On 28 Aug 2019, at 20:43, Tibor Digana  wrote:
>> >
>> > I used Maven 3.6.2 in the IntelliJ IDEA 2019.2.1 and I found these
>> errors
>> > in the log file:
>> > ~/.IntelliJIdea2019.2/system/log/idea.log
>> >
>> > 2019-08-28 21:31:32,072 [255937677]  ERROR -
>> #org.jetbrains.idea.maven
>> > - com.google.inject.CreationException: Unable to create injector, see
>> the
>> > following errors:
>> >
>> > 1) No implementation for org.apache.maven.model.path.PathTranslator was
>> > bound.
>> >  while locating org.apache.maven.model.path.PathTranslator
>> >for field at
>> >
>> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.pathTranslator(Unknown
>> > Source)
>> >  at
>> >
>> org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)
>> >
>> > 2) No implementation for org.apache.maven.model.path.UrlNormalizer was
>> > bound.
>> >  while locating org.apache.maven.model.path.UrlNormalizer
>> >for field at
>> >
>> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.urlNormalizer(Unknown
>> > Source)
>> >  at
>> >
>> org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)
>> >
>> > 2 errors
>> > java.lang.RuntimeException: com.google.inject.CreationException: Unable
>> to
>> > create injector, see the following errors:
>> >
>> > 1) No implementation for org.apache.maven.model.path.PathTranslator was
>> > bound.
>> >  while locating org.apache.maven.model.path.PathTranslator
>> >for field at
>> >
>> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.pathTranslator(Unknown
>> > Source)
>> >  at
>> >
>> org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)
>> >
>> > 2) No implementation for org.apache.maven.model.path.UrlNormalizer was
>> > bound.
>> >  while locating org.apache.maven.model.path.UrlNormalizer
>> >for field at
>> >
>> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.urlNormalizer(Unknown
>> > Source)
>> >  at
>> >
>> org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)
>> >
>> > 2 errors
>> > at
>> >
>> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
>> > at
>> >
>> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:159)
>> > at
>> >
>> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
>> > at com.google.inject.Guice.createInjector(Guice.java:87)
>> > at com.google.inject.Guice.createInjector(Guice.java:69)
>> > at com.google.inject.Guice.createInjector(Guice.java:59)
>> > at
>> >
>> org.codehaus.plexus.DefaultPlexusContainer.addComponent(DefaultPlexusContainer.java:344)
>> > at
>> >
>> org.codehaus.plexus.DefaultPlexusContainer.addComponent(DefaultPlexusContainer.java:332)
>> > at
>> >
>> org.jetbrains.idea.maven.server.Maven3XServerEmbedder.customizeComponents(Maven3XServerEmbedder.java:573)
>> > at
>> >
>> org.jetbrains.idea.maven.server.Maven3XServerEmbedder.customize(Maven3XServerEmbedder.java:542)
>> > at
>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
>> > Method)
>> > at
>> >
>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> > at
>> >
>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> > at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>> > at
>> >
>> java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359)
>> > at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200)
>> > at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197)
>> > at 

Re: Found Issues - Release Apache Maven Version 3.6.2

2019-08-28 Thread Tibor Digana
I do not have NPE in the log.
Guice is certainly not CDI. Moving Guice to CDI must be painful.
One reason why PathTranslator could not be found is that there are several
bean instances of the same interface.
Second problem might go with the Guice/CDI.
See this inheritance:

@Named
@Singleton
public class DefaultPathTranslator
implements PathTranslator
{

public interface PathTranslator
{



On Wed, Aug 28, 2019 at 10:04 PM Filipe Sousa  wrote:

> Hi,
>
> Not sure if it’s the same bug I commented in
> https://issues.apache.org/jira/browse/MNG-6638?focusedCommentId=16852351=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16852351
>
> I reported to Jetbrains https://youtrack.jetbrains.com/issue/IDEA-215315 <
> https://youtrack.jetbrains.com/issue/IDEA-215315> and is supposed to be
> fixed in 2019.3
>
> > On 28 Aug 2019, at 20:43, Tibor Digana  wrote:
> >
> > I used Maven 3.6.2 in the IntelliJ IDEA 2019.2.1 and I found these errors
> > in the log file:
> > ~/.IntelliJIdea2019.2/system/log/idea.log
> >
> > 2019-08-28 21:31:32,072 [255937677]  ERROR -
> #org.jetbrains.idea.maven
> > - com.google.inject.CreationException: Unable to create injector, see the
> > following errors:
> >
> > 1) No implementation for org.apache.maven.model.path.PathTranslator was
> > bound.
> >  while locating org.apache.maven.model.path.PathTranslator
> >for field at
> >
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.pathTranslator(Unknown
> > Source)
> >  at
> >
> org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)
> >
> > 2) No implementation for org.apache.maven.model.path.UrlNormalizer was
> > bound.
> >  while locating org.apache.maven.model.path.UrlNormalizer
> >for field at
> >
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.urlNormalizer(Unknown
> > Source)
> >  at
> >
> org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)
> >
> > 2 errors
> > java.lang.RuntimeException: com.google.inject.CreationException: Unable
> to
> > create injector, see the following errors:
> >
> > 1) No implementation for org.apache.maven.model.path.PathTranslator was
> > bound.
> >  while locating org.apache.maven.model.path.PathTranslator
> >for field at
> >
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.pathTranslator(Unknown
> > Source)
> >  at
> >
> org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)
> >
> > 2) No implementation for org.apache.maven.model.path.UrlNormalizer was
> > bound.
> >  while locating org.apache.maven.model.path.UrlNormalizer
> >for field at
> >
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.urlNormalizer(Unknown
> > Source)
> >  at
> >
> org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)
> >
> > 2 errors
> > at
> >
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
> > at
> >
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:159)
> > at
> >
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
> > at com.google.inject.Guice.createInjector(Guice.java:87)
> > at com.google.inject.Guice.createInjector(Guice.java:69)
> > at com.google.inject.Guice.createInjector(Guice.java:59)
> > at
> >
> org.codehaus.plexus.DefaultPlexusContainer.addComponent(DefaultPlexusContainer.java:344)
> > at
> >
> org.codehaus.plexus.DefaultPlexusContainer.addComponent(DefaultPlexusContainer.java:332)
> > at
> >
> org.jetbrains.idea.maven.server.Maven3XServerEmbedder.customizeComponents(Maven3XServerEmbedder.java:573)
> > at
> >
> org.jetbrains.idea.maven.server.Maven3XServerEmbedder.customize(Maven3XServerEmbedder.java:542)
> > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> > Method)
> > at
> >
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > at
> >
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> > at
> >
> java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359)
> > at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200)
> > at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197)
> > at java.base/java.security.AccessController.doPrivileged(Native Method)
> > at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> > at
> >
> java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562)
> > at
> >
> java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796)
> > at
> >
> java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677)
> > at 

Re: Found Issues - Release Apache Maven Version 3.6.2

2019-08-28 Thread Filipe Sousa
Hi,

Not sure if it’s the same bug I commented in 
https://issues.apache.org/jira/browse/MNG-6638?focusedCommentId=16852351=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16852351

I reported to Jetbrains https://youtrack.jetbrains.com/issue/IDEA-215315 
 and is supposed to be fixed 
in 2019.3

> On 28 Aug 2019, at 20:43, Tibor Digana  wrote:
> 
> I used Maven 3.6.2 in the IntelliJ IDEA 2019.2.1 and I found these errors
> in the log file:
> ~/.IntelliJIdea2019.2/system/log/idea.log
> 
> 2019-08-28 21:31:32,072 [255937677]  ERROR -  #org.jetbrains.idea.maven
> - com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 
> 1) No implementation for org.apache.maven.model.path.PathTranslator was
> bound.
>  while locating org.apache.maven.model.path.PathTranslator
>for field at
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.pathTranslator(Unknown
> Source)
>  at
> org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)
> 
> 2) No implementation for org.apache.maven.model.path.UrlNormalizer was
> bound.
>  while locating org.apache.maven.model.path.UrlNormalizer
>for field at
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.urlNormalizer(Unknown
> Source)
>  at
> org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)
> 
> 2 errors
> java.lang.RuntimeException: com.google.inject.CreationException: Unable to
> create injector, see the following errors:
> 
> 1) No implementation for org.apache.maven.model.path.PathTranslator was
> bound.
>  while locating org.apache.maven.model.path.PathTranslator
>for field at
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.pathTranslator(Unknown
> Source)
>  at
> org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)
> 
> 2) No implementation for org.apache.maven.model.path.UrlNormalizer was
> bound.
>  while locating org.apache.maven.model.path.UrlNormalizer
>for field at
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.urlNormalizer(Unknown
> Source)
>  at
> org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)
> 
> 2 errors
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:159)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
> at com.google.inject.Guice.createInjector(Guice.java:87)
> at com.google.inject.Guice.createInjector(Guice.java:69)
> at com.google.inject.Guice.createInjector(Guice.java:59)
> at
> org.codehaus.plexus.DefaultPlexusContainer.addComponent(DefaultPlexusContainer.java:344)
> at
> org.codehaus.plexus.DefaultPlexusContainer.addComponent(DefaultPlexusContainer.java:332)
> at
> org.jetbrains.idea.maven.server.Maven3XServerEmbedder.customizeComponents(Maven3XServerEmbedder.java:573)
> at
> org.jetbrains.idea.maven.server.Maven3XServerEmbedder.customize(Maven3XServerEmbedder.java:542)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359)
> at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200)
> at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562)
> at
> java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796)
> at
> java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> at
> java.rmi/sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:283)
> at
> java.rmi/sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:260)
> at java.rmi/sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161)
> at
> 

Found Issues - Release Apache Maven Version 3.6.2

2019-08-28 Thread Tibor Digana
I used Maven 3.6.2 in the IntelliJ IDEA 2019.2.1 and I found these errors
in the log file:
~/.IntelliJIdea2019.2/system/log/idea.log

2019-08-28 21:31:32,072 [255937677]  ERROR -  #org.jetbrains.idea.maven
- com.google.inject.CreationException: Unable to create injector, see the
following errors:

1) No implementation for org.apache.maven.model.path.PathTranslator was
bound.
  while locating org.apache.maven.model.path.PathTranslator
for field at
org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.pathTranslator(Unknown
Source)
  at
org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)

2) No implementation for org.apache.maven.model.path.UrlNormalizer was
bound.
  while locating org.apache.maven.model.path.UrlNormalizer
for field at
org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.urlNormalizer(Unknown
Source)
  at
org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)

2 errors
java.lang.RuntimeException: com.google.inject.CreationException: Unable to
create injector, see the following errors:

1) No implementation for org.apache.maven.model.path.PathTranslator was
bound.
  while locating org.apache.maven.model.path.PathTranslator
for field at
org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.pathTranslator(Unknown
Source)
  at
org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)

2) No implementation for org.apache.maven.model.path.UrlNormalizer was
bound.
  while locating org.apache.maven.model.path.UrlNormalizer
for field at
org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator.urlNormalizer(Unknown
Source)
  at
org.codehaus.plexus.DefaultPlexusContainer$1.configure(DefaultPlexusContainer.java:350)

2 errors
at
com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
at
com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:159)
at
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
at com.google.inject.Guice.createInjector(Guice.java:87)
at com.google.inject.Guice.createInjector(Guice.java:69)
at com.google.inject.Guice.createInjector(Guice.java:59)
at
org.codehaus.plexus.DefaultPlexusContainer.addComponent(DefaultPlexusContainer.java:344)
at
org.codehaus.plexus.DefaultPlexusContainer.addComponent(DefaultPlexusContainer.java:332)
at
org.jetbrains.idea.maven.server.Maven3XServerEmbedder.customizeComponents(Maven3XServerEmbedder.java:573)
at
org.jetbrains.idea.maven.server.Maven3XServerEmbedder.customize(Maven3XServerEmbedder.java:542)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359)
at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200)
at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196)
at
java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562)
at
java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796)
at
java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at
java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
at
java.rmi/sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:283)
at
java.rmi/sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:260)
at java.rmi/sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161)
at
java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:209)
at
java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:161)
at com.sun.proxy.$Proxy216.customize(Unknown Source)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at 

Re: [VOTE] Release Apache Maven Version 3.6.2

2019-08-28 Thread Tibor Digana
+1, sha512 ok, build ok, found error - see the extra email.

On Wed, Aug 28, 2019 at 9:18 PM Enrico Olivelli  wrote:

> Hi,
>
> We have solved 52 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12345234
>
> There are issues left in JIRA for Maven core:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1529
>
> The distributable binaries and sources can be found here:
>
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/
>
> Specifically the zip, tarball and source archives can be found here:
>
>
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-bin.zip
>
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-bin.tar.gz
>
>
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-src.zip
>
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-src.tar.gz
>
> The release artifacts are staged for distribution in:
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.2
>
> Source release checksum(s):
> apache-maven-3.6.2-src.tar.gz
>
>sha1: 373ffbe9fc88e5facbe10d7a6f6badd243545ade
> sha512:
>
> 235198b48d29fe2f2394f2607a9a1637acfd0286beacb974c566f7f36ac6c469871a0db287539b2b62e6322d7423f586949e41cbbfea330fe03bf690688f6fd7
>
> apache-maven-3.6.2-src.zip:
>
>sha1: c6c5bd9828b3350905e97177978724eed0698de3
> sha512:
>
> d7fdafbc16bd547bc3c2513255df375c2a616b04d414c2ffd7d9deb9931fab5db4c7ac912cc4bb0d96d0a083560b3cc1848ea9eecc3aeb4e4c5184329a7ead5b
>
> Git tag:
>
> https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=40f52333136460af0dc0d7232c0dc0bcf0d9e117
>
> Staging site:
> https://maven.apache.org/components/ref/3-LATEST/
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Kind regards
> Enrico Olivelli
>


Re: [VOTE] Release Apache Maven Version 3.6.2

2019-08-28 Thread jesper

+1

On 28.08.2019 21:17, Enrico Olivelli wrote:

Hi,

We have solved 52 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12345234

There are issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1529

The distributable binaries and sources can be found here:
https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/

Specifically the zip, tarball and source archives can be found here:

https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-bin.zip
https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-bin.tar.gz

https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-src.zip
https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-src.tar.gz

The release artifacts are staged for distribution in:
https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.2

Source release checksum(s):
apache-maven-3.6.2-src.tar.gz

   sha1: 373ffbe9fc88e5facbe10d7a6f6badd243545ade
sha512:
235198b48d29fe2f2394f2607a9a1637acfd0286beacb974c566f7f36ac6c469871a0db287539b2b62e6322d7423f586949e41cbbfea330fe03bf690688f6fd7

apache-maven-3.6.2-src.zip:

   sha1: c6c5bd9828b3350905e97177978724eed0698de3
sha512:
d7fdafbc16bd547bc3c2513255df375c2a616b04d414c2ffd7d9deb9931fab5db4c7ac912cc4bb0d96d0a083560b3cc1848ea9eecc3aeb4e4c5184329a7ead5b

Git tag:
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=40f52333136460af0dc0d7232c0dc0bcf0d9e117

Staging site:
https://maven.apache.org/components/ref/3-LATEST/

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Kind regards
Enrico Olivelli


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



[VOTE] Release Apache Maven Version 3.6.2

2019-08-28 Thread Enrico Olivelli
Hi,

We have solved 52 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12345234

There are issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1529

The distributable binaries and sources can be found here:
https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/

Specifically the zip, tarball and source archives can be found here:

https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-bin.zip
https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-bin.tar.gz

https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-src.zip
https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-src.tar.gz

The release artifacts are staged for distribution in:
https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.2

Source release checksum(s):
apache-maven-3.6.2-src.tar.gz

   sha1: 373ffbe9fc88e5facbe10d7a6f6badd243545ade
sha512:
235198b48d29fe2f2394f2607a9a1637acfd0286beacb974c566f7f36ac6c469871a0db287539b2b62e6322d7423f586949e41cbbfea330fe03bf690688f6fd7

apache-maven-3.6.2-src.zip:

   sha1: c6c5bd9828b3350905e97177978724eed0698de3
sha512:
d7fdafbc16bd547bc3c2513255df375c2a616b04d414c2ffd7d9deb9931fab5db4c7ac912cc4bb0d96d0a083560b3cc1848ea9eecc3aeb4e4c5184329a7ead5b

Git tag:
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=40f52333136460af0dc0d7232c0dc0bcf0d9e117

Staging site:
https://maven.apache.org/components/ref/3-LATEST/

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Kind regards
Enrico Olivelli


Re: Guidance for Maven Core release

2019-08-28 Thread Enrico Olivelli
Il mer 28 ago 2019, 20:55 Karl Heinz Marbaise  ha
scritto:

> Hi Enrico,
>
> On 28.08.19 19:52, Enrico Olivelli wrote:
> > Thank you Mirko
> > I have sent the official VOTE email.
>
> Unfortunately I don't see the VOTE mail ? Or did I miss something ?
>
Ops
Gmail to Apache SMTP proxy had a problem.
I will resend the email.

Thanks

Enrico



> Kind regards
> Karl Heinz Marbaise
>
> > I am now preparing the "release notes" with the summary for the website.
> > It will take time, in the meanwhile we can all the the staged artifacts
> >
> > Enrico
> >
> > Il giorno mer 28 ago 2019 alle ore 18:29 Mirko Friedenhagen <
> > mfriedenha...@gmx.de> ha scritto:
> >
> >> Hello Enrico,
> >>
> >> * just a short thumbs up, I had used 3.6.2-SNAPSHOT in about 10 projects
> >> calling `mvn verify` in parallel and had no issues.
> >> * Today these builds broke because now it is 3.6.3-SNAPSHOT.
> >> * I am just in the process of testing 3.6.2 with above mentioned
> projects.
> >> * I will report back as well once you started the vote.
> >>
> >> Regards
> >> Mirko
> >>
> >>> Am 28.08.2019 um 12:34 schrieb Enrico Olivelli :
> >>>
> >>> Il giorno mar 27 ago 2019 alle ore 19:21 Karl Heinz Marbaise <
> >>> khmarba...@gmx.de> ha scritto:
> >>>
>  Hi Enrico,
> 
>  On 27.08.19 18:53, Enrico Olivelli wrote:
> > I have created the tag so the master is ready for new commits.
> > I am testing the staged artifacts, It will take time.
> 
>  Can you send the staged artifacts URL's so I can test too ?
> 
> >>>
> >>> Sure
> >>> Here you are:
> >>> Dist area:
> >>> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.2
> >>>
> >>> Apache Repository
> >>>
> >>
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/
> >>>
> >>> Staged site:
> >>> https://maven.apache.org/components/ref/3-LATEST/
> >>>
> >>> I would like to publish Integration tests results Hervè is helping me
> >>>
> >>> Enrico
> >>>
> >>>
> >>>
> 
>  Kind regards
>  Karl Heinz Marbaise
> 
> > I will send the VOTE email as soon as I am ready.
> >
> > Enrico
> >
> > Il giorno dom 25 ago 2019 alle ore 20:27 Enrico Olivelli
> > mailto:eolive...@gmail.com>> ha scritto:
> >
> > Thank you guys for your support.
> > I apologize, something came up, I can't start the procedure until
> > (hopefully) Wednesday.
> >
> > I will start as soon as possible.
> > Please tag me if you are committing something to master branch
> >
> > Cheers
> > Enrico
> >
> > Il giorno dom 25 ago 2019 alle ore 12:53 Karl Heinz Marbaise
> > mailto:khmarba...@gmx.de>> ha scritto:
> >
> > Hi Enrico,
> >
> > On 24.08.19 23:55, Enrico Olivelli wrote:
> >> Hello,
> >> As I going to start the release procedure for Maven Core I
> > have a bunch of
> >> questions.
> >> I see  that the procedure is slightly different from the
> > procedure for
> >> plugins ([1]), but actually the main differences are about
> > the way we stage
> >> the release artifacts and the finalization phase, the core of
> > the processs
> >> will be release:prepare and release:perform as usual.
> >>
> >> So I will run "mvn:perform" and I will copy the artifacts to
> > [4], that is
> >> in a directory named 3.6.2 (I see that Karl used 3.6.0 last
> > time for 3.6.1,
> >> maybe it was a typo).
> >> I will run manually the integration tests against the binary
> > artifacts
> >> generated and perform my self tests, if I have some problem
> > can I drop the
> >> get tag and the staged repository or should I ban "3.6.2" tag
> > forever and
> >> move immediately to 3.6.3 ?
> >>
> >> I see that Karl last time ([2]) sent a mail slightly
> > different from the
> >> template  [3] shall I use that email as template ?
> >>
> >> How does website staging works for Maven Core ? I see no
>  specific
> >> instructions here in [6], I think the directory for Maven
> > Core staging is
> >> [7] (According to the
> > component-reference-documentation-helper tool).
> >> I have also found this script from Hervé, see [9], it runs
> > the same
> >> commands as in the "common" procedure
> >>
> >> Release notes:
> >> I can't find release notes for 3.6.0 and 3.6.1 on svn [8],
> > have the sources
> >> been moved to another location ? on some git repo ?
> >>
> >> Should I prepare the release notes before then I cut the
> > release and send
> >> the VOTE, or can I create them during the finalization of the
> > release ?
> >> It will take time to write those notes, but I also think that
> > writing the
> >> 

Re: Guidance for Maven Core release

2019-08-28 Thread Karl Heinz Marbaise

Hi Enrico,

On 28.08.19 19:52, Enrico Olivelli wrote:

Thank you Mirko
I have sent the official VOTE email.


Unfortunately I don't see the VOTE mail ? Or did I miss something ?

Kind regards
Karl Heinz Marbaise


I am now preparing the "release notes" with the summary for the website.
It will take time, in the meanwhile we can all the the staged artifacts

Enrico

Il giorno mer 28 ago 2019 alle ore 18:29 Mirko Friedenhagen <
mfriedenha...@gmx.de> ha scritto:


Hello Enrico,

* just a short thumbs up, I had used 3.6.2-SNAPSHOT in about 10 projects
calling `mvn verify` in parallel and had no issues.
* Today these builds broke because now it is 3.6.3-SNAPSHOT.
* I am just in the process of testing 3.6.2 with above mentioned projects.
* I will report back as well once you started the vote.

Regards
Mirko


Am 28.08.2019 um 12:34 schrieb Enrico Olivelli :

Il giorno mar 27 ago 2019 alle ore 19:21 Karl Heinz Marbaise <
khmarba...@gmx.de> ha scritto:


Hi Enrico,

On 27.08.19 18:53, Enrico Olivelli wrote:

I have created the tag so the master is ready for new commits.
I am testing the staged artifacts, It will take time.


Can you send the staged artifacts URL's so I can test too ?



Sure
Here you are:
Dist area:
https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.2

Apache Repository


https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/


Staged site:
https://maven.apache.org/components/ref/3-LATEST/

I would like to publish Integration tests results Hervè is helping me

Enrico





Kind regards
Karl Heinz Marbaise


I will send the VOTE email as soon as I am ready.

Enrico

Il giorno dom 25 ago 2019 alle ore 20:27 Enrico Olivelli
mailto:eolive...@gmail.com>> ha scritto:

Thank you guys for your support.
I apologize, something came up, I can't start the procedure until
(hopefully) Wednesday.

I will start as soon as possible.
Please tag me if you are committing something to master branch

Cheers
Enrico

Il giorno dom 25 ago 2019 alle ore 12:53 Karl Heinz Marbaise
mailto:khmarba...@gmx.de>> ha scritto:

Hi Enrico,

On 24.08.19 23:55, Enrico Olivelli wrote:

Hello,
As I going to start the release procedure for Maven Core I

have a bunch of

questions.
I see  that the procedure is slightly different from the

procedure for

plugins ([1]), but actually the main differences are about

the way we stage

the release artifacts and the finalization phase, the core of

the processs

will be release:prepare and release:perform as usual.

So I will run "mvn:perform" and I will copy the artifacts to

[4], that is

in a directory named 3.6.2 (I see that Karl used 3.6.0 last

time for 3.6.1,

maybe it was a typo).
I will run manually the integration tests against the binary

artifacts

generated and perform my self tests, if I have some problem

can I drop the

get tag and the staged repository or should I ban "3.6.2" tag

forever and

move immediately to 3.6.3 ?

I see that Karl last time ([2]) sent a mail slightly

different from the

template  [3] shall I use that email as template ?

How does website staging works for Maven Core ? I see no

specific

instructions here in [6], I think the directory for Maven

Core staging is

[7] (According to the

component-reference-documentation-helper tool).

I have also found this script from Hervé, see [9], it runs

the same

commands as in the "common" procedure

Release notes:
I can't find release notes for 3.6.0 and 3.6.1 on svn [8],

have the sources

been moved to another location ? on some git repo ?

Should I prepare the release notes before then I cut the

release and send

the VOTE, or can I create them during the finalization of the

release ?

It will take time to write those notes, but I also think that

writing the

release notes helps a lot in understanding the effective

contents of the

release.


I have started a new build of master branch now, in order to

perform a

final check up, see[5].

I am sorry if this list was so long but I feel it is a big

responsibility

to cut a release of Maven core and I want to be sure I am

understanding

clearly what I am doing.


No need to apologize cause based on the list you are asking you
show how
serious you are taking this ...

No problem..

As Hervé already stated go for it...

Kind regards
Karl Heinz Marbaise



Please do not push changes to master branch and let me drive

all of the

commits until the release procedure is completed.

Best regards
Enrico Olivelli


[1]



https://maven.apache.org/developers/release/maven-core-release.html

[2]






https://lists.apache.org/thread.html/249091304adb6366845ba115fb3d1d9d358682630ab4a51df0d4bf67@%3Cdev.maven.apache.org%3E

[3]







Re: Guidance for Maven Core release

2019-08-28 Thread Enrico Olivelli
Thank you Mirko
I have sent the official VOTE email.
I am now preparing the "release notes" with the summary for the website.
It will take time, in the meanwhile we can all the the staged artifacts

Enrico

Il giorno mer 28 ago 2019 alle ore 18:29 Mirko Friedenhagen <
mfriedenha...@gmx.de> ha scritto:

> Hello Enrico,
>
> * just a short thumbs up, I had used 3.6.2-SNAPSHOT in about 10 projects
> calling `mvn verify` in parallel and had no issues.
> * Today these builds broke because now it is 3.6.3-SNAPSHOT.
> * I am just in the process of testing 3.6.2 with above mentioned projects.
> * I will report back as well once you started the vote.
>
> Regards
> Mirko
>
> > Am 28.08.2019 um 12:34 schrieb Enrico Olivelli :
> >
> > Il giorno mar 27 ago 2019 alle ore 19:21 Karl Heinz Marbaise <
> > khmarba...@gmx.de> ha scritto:
> >
> >> Hi Enrico,
> >>
> >> On 27.08.19 18:53, Enrico Olivelli wrote:
> >>> I have created the tag so the master is ready for new commits.
> >>> I am testing the staged artifacts, It will take time.
> >>
> >> Can you send the staged artifacts URL's so I can test too ?
> >>
> >
> > Sure
> > Here you are:
> > Dist area:
> > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.2
> >
> > Apache Repository
> >
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/
> >
> > Staged site:
> > https://maven.apache.org/components/ref/3-LATEST/
> >
> > I would like to publish Integration tests results Hervè is helping me
> >
> > Enrico
> >
> >
> >
> >>
> >> Kind regards
> >> Karl Heinz Marbaise
> >>
> >>> I will send the VOTE email as soon as I am ready.
> >>>
> >>> Enrico
> >>>
> >>> Il giorno dom 25 ago 2019 alle ore 20:27 Enrico Olivelli
> >>> mailto:eolive...@gmail.com>> ha scritto:
> >>>
> >>>Thank you guys for your support.
> >>>I apologize, something came up, I can't start the procedure until
> >>>(hopefully) Wednesday.
> >>>
> >>>I will start as soon as possible.
> >>>Please tag me if you are committing something to master branch
> >>>
> >>>Cheers
> >>>Enrico
> >>>
> >>>Il giorno dom 25 ago 2019 alle ore 12:53 Karl Heinz Marbaise
> >>>mailto:khmarba...@gmx.de>> ha scritto:
> >>>
> >>>Hi Enrico,
> >>>
> >>>On 24.08.19 23:55, Enrico Olivelli wrote:
>  Hello,
>  As I going to start the release procedure for Maven Core I
> >>>have a bunch of
>  questions.
>  I see  that the procedure is slightly different from the
> >>>procedure for
>  plugins ([1]), but actually the main differences are about
> >>>the way we stage
>  the release artifacts and the finalization phase, the core of
> >>>the processs
>  will be release:prepare and release:perform as usual.
> 
>  So I will run "mvn:perform" and I will copy the artifacts to
> >>>[4], that is
>  in a directory named 3.6.2 (I see that Karl used 3.6.0 last
> >>>time for 3.6.1,
>  maybe it was a typo).
>  I will run manually the integration tests against the binary
> >>>artifacts
>  generated and perform my self tests, if I have some problem
> >>>can I drop the
>  get tag and the staged repository or should I ban "3.6.2" tag
> >>>forever and
>  move immediately to 3.6.3 ?
> 
>  I see that Karl last time ([2]) sent a mail slightly
> >>>different from the
>  template  [3] shall I use that email as template ?
> 
>  How does website staging works for Maven Core ? I see no
> >> specific
>  instructions here in [6], I think the directory for Maven
> >>>Core staging is
>  [7] (According to the
> >>>component-reference-documentation-helper tool).
>  I have also found this script from Hervé, see [9], it runs
> >>>the same
>  commands as in the "common" procedure
> 
>  Release notes:
>  I can't find release notes for 3.6.0 and 3.6.1 on svn [8],
> >>>have the sources
>  been moved to another location ? on some git repo ?
> 
>  Should I prepare the release notes before then I cut the
> >>>release and send
>  the VOTE, or can I create them during the finalization of the
> >>>release ?
>  It will take time to write those notes, but I also think that
> >>>writing the
>  release notes helps a lot in understanding the effective
> >>>contents of the
>  release.
> 
> 
>  I have started a new build of master branch now, in order to
> >>>perform a
>  final check up, see[5].
> 
>  I am sorry if this list was so long but I feel it is a big
> >>>responsibility
>  to cut a release of Maven core and I want to be sure I am
> >>>understanding
>  clearly what I am doing.
> >>>
> >>>No need to apologize cause based on the list you are asking you
> >>>show how
> >>>serious you are taking this ...
> >>>
> >>>No problem..
> >>>

Re: Guidance for Maven Core release

2019-08-28 Thread Mirko Friedenhagen
Hello Enrico,

* just a short thumbs up, I had used 3.6.2-SNAPSHOT in about 10 projects 
calling `mvn verify` in parallel and had no issues.
* Today these builds broke because now it is 3.6.3-SNAPSHOT.
* I am just in the process of testing 3.6.2 with above mentioned projects.
* I will report back as well once you started the vote.

Regards
Mirko

> Am 28.08.2019 um 12:34 schrieb Enrico Olivelli :
> 
> Il giorno mar 27 ago 2019 alle ore 19:21 Karl Heinz Marbaise <
> khmarba...@gmx.de> ha scritto:
> 
>> Hi Enrico,
>> 
>> On 27.08.19 18:53, Enrico Olivelli wrote:
>>> I have created the tag so the master is ready for new commits.
>>> I am testing the staged artifacts, It will take time.
>> 
>> Can you send the staged artifacts URL's so I can test too ?
>> 
> 
> Sure
> Here you are:
> Dist area:
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.2
> 
> Apache Repository
> https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/
> 
> Staged site:
> https://maven.apache.org/components/ref/3-LATEST/
> 
> I would like to publish Integration tests results Hervè is helping me
> 
> Enrico
> 
> 
> 
>> 
>> Kind regards
>> Karl Heinz Marbaise
>> 
>>> I will send the VOTE email as soon as I am ready.
>>> 
>>> Enrico
>>> 
>>> Il giorno dom 25 ago 2019 alle ore 20:27 Enrico Olivelli
>>> mailto:eolive...@gmail.com>> ha scritto:
>>> 
>>>Thank you guys for your support.
>>>I apologize, something came up, I can't start the procedure until
>>>(hopefully) Wednesday.
>>> 
>>>I will start as soon as possible.
>>>Please tag me if you are committing something to master branch
>>> 
>>>Cheers
>>>Enrico
>>> 
>>>Il giorno dom 25 ago 2019 alle ore 12:53 Karl Heinz Marbaise
>>>mailto:khmarba...@gmx.de>> ha scritto:
>>> 
>>>Hi Enrico,
>>> 
>>>On 24.08.19 23:55, Enrico Olivelli wrote:
 Hello,
 As I going to start the release procedure for Maven Core I
>>>have a bunch of
 questions.
 I see  that the procedure is slightly different from the
>>>procedure for
 plugins ([1]), but actually the main differences are about
>>>the way we stage
 the release artifacts and the finalization phase, the core of
>>>the processs
 will be release:prepare and release:perform as usual.
 
 So I will run "mvn:perform" and I will copy the artifacts to
>>>[4], that is
 in a directory named 3.6.2 (I see that Karl used 3.6.0 last
>>>time for 3.6.1,
 maybe it was a typo).
 I will run manually the integration tests against the binary
>>>artifacts
 generated and perform my self tests, if I have some problem
>>>can I drop the
 get tag and the staged repository or should I ban "3.6.2" tag
>>>forever and
 move immediately to 3.6.3 ?
 
 I see that Karl last time ([2]) sent a mail slightly
>>>different from the
 template  [3] shall I use that email as template ?
 
 How does website staging works for Maven Core ? I see no
>> specific
 instructions here in [6], I think the directory for Maven
>>>Core staging is
 [7] (According to the
>>>component-reference-documentation-helper tool).
 I have also found this script from Hervé, see [9], it runs
>>>the same
 commands as in the "common" procedure
 
 Release notes:
 I can't find release notes for 3.6.0 and 3.6.1 on svn [8],
>>>have the sources
 been moved to another location ? on some git repo ?
 
 Should I prepare the release notes before then I cut the
>>>release and send
 the VOTE, or can I create them during the finalization of the
>>>release ?
 It will take time to write those notes, but I also think that
>>>writing the
 release notes helps a lot in understanding the effective
>>>contents of the
 release.
 
 
 I have started a new build of master branch now, in order to
>>>perform a
 final check up, see[5].
 
 I am sorry if this list was so long but I feel it is a big
>>>responsibility
 to cut a release of Maven core and I want to be sure I am
>>>understanding
 clearly what I am doing.
>>> 
>>>No need to apologize cause based on the list you are asking you
>>>show how
>>>serious you are taking this ...
>>> 
>>>No problem..
>>> 
>>>As Hervé already stated go for it...
>>> 
>>>Kind regards
>>>Karl Heinz Marbaise
>>> 
 
 Please do not push changes to master branch and let me drive
>>>all of the
 commits until the release procedure is completed.
 
 Best regards
 Enrico Olivelli
 
 
 [1]
>>> 
>> https://maven.apache.org/developers/release/maven-core-release.html
 [2]
 
>>> 
>> https://lists.apache.org/thread.html/249091304adb6366845ba115fb3d1d9d358682630ab4a51df0d4bf67@%3Cdev.maven.apache.org%3E

Re: Guidance for Maven Core release

2019-08-28 Thread Enrico Olivelli
Il giorno mar 27 ago 2019 alle ore 19:21 Karl Heinz Marbaise <
khmarba...@gmx.de> ha scritto:

> Hi Enrico,
>
> On 27.08.19 18:53, Enrico Olivelli wrote:
> > I have created the tag so the master is ready for new commits.
> > I am testing the staged artifacts, It will take time.
>
> Can you send the staged artifacts URL's so I can test too ?
>

Sure
Here you are:
Dist area:
https://dist.apache.org/repos/dist/dev/maven/maven-3/3.6.2

Apache Repository
https://repository.apache.org/content/repositories/maven-1529/org/apache/maven/apache-maven/3.6.2/

Staged site:
https://maven.apache.org/components/ref/3-LATEST/

I would like to publish Integration tests results Hervè is helping me

Enrico



>
> Kind regards
> Karl Heinz Marbaise
>
> > I will send the VOTE email as soon as I am ready.
> >
> > Enrico
> >
> > Il giorno dom 25 ago 2019 alle ore 20:27 Enrico Olivelli
> > mailto:eolive...@gmail.com>> ha scritto:
> >
> > Thank you guys for your support.
> > I apologize, something came up, I can't start the procedure until
> > (hopefully) Wednesday.
> >
> > I will start as soon as possible.
> > Please tag me if you are committing something to master branch
> >
> > Cheers
> > Enrico
> >
> > Il giorno dom 25 ago 2019 alle ore 12:53 Karl Heinz Marbaise
> > mailto:khmarba...@gmx.de>> ha scritto:
> >
> > Hi Enrico,
> >
> > On 24.08.19 23:55, Enrico Olivelli wrote:
> >  > Hello,
> >  > As I going to start the release procedure for Maven Core I
> > have a bunch of
> >  > questions.
> >  > I see  that the procedure is slightly different from the
> > procedure for
> >  > plugins ([1]), but actually the main differences are about
> > the way we stage
> >  > the release artifacts and the finalization phase, the core of
> > the processs
> >  > will be release:prepare and release:perform as usual.
> >  >
> >  > So I will run "mvn:perform" and I will copy the artifacts to
> > [4], that is
> >  > in a directory named 3.6.2 (I see that Karl used 3.6.0 last
> > time for 3.6.1,
> >  > maybe it was a typo).
> >  > I will run manually the integration tests against the binary
> > artifacts
> >  > generated and perform my self tests, if I have some problem
> > can I drop the
> >  > get tag and the staged repository or should I ban "3.6.2" tag
> > forever and
> >  > move immediately to 3.6.3 ?
> >  >
> >  > I see that Karl last time ([2]) sent a mail slightly
> > different from the
> >  > template  [3] shall I use that email as template ?
> >  >
> >  > How does website staging works for Maven Core ? I see no
> specific
> >  > instructions here in [6], I think the directory for Maven
> > Core staging is
> >  > [7] (According to the
> > component-reference-documentation-helper tool).
> >  > I have also found this script from Hervé, see [9], it runs
> > the same
> >  > commands as in the "common" procedure
> >  >
> >  > Release notes:
> >  > I can't find release notes for 3.6.0 and 3.6.1 on svn [8],
> > have the sources
> >  > been moved to another location ? on some git repo ?
> >  >
> >  > Should I prepare the release notes before then I cut the
> > release and send
> >  > the VOTE, or can I create them during the finalization of the
> > release ?
> >  > It will take time to write those notes, but I also think that
> > writing the
> >  > release notes helps a lot in understanding the effective
> > contents of the
> >  > release.
> >  >
> >  >
> >  > I have started a new build of master branch now, in order to
> > perform a
> >  > final check up, see[5].
> >  >
> >  > I am sorry if this list was so long but I feel it is a big
> > responsibility
> >  > to cut a release of Maven core and I want to be sure I am
> > understanding
> >  > clearly what I am doing.
> >
> > No need to apologize cause based on the list you are asking you
> > show how
> > serious you are taking this ...
> >
> > No problem..
> >
> > As Hervé already stated go for it...
> >
> > Kind regards
> > Karl Heinz Marbaise
> >
> >  >
> >  > Please do not push changes to master branch and let me drive
> > all of the
> >  > commits until the release procedure is completed.
> >  >
> >  > Best regards
> >  > Enrico Olivelli
> >  >
> >  >
> >  > [1]
> >
> https://maven.apache.org/developers/release/maven-core-release.html
> >  > [2]
> >  >
> >
>