Hi,
The vote has passed with the following result:
+1 :Karl Heinz Marbaise, Robert Scholte, Stephen Connolly, Hervé Boutemy
PMC quorum: reached
I will promote the artifacts to the central repo.
Regards,
Hervé
Le dimanche 22 janvier 2017, 16:41:44 CET Hervé BOUTEMY a écrit :
> Hi,
>
> We
+1
Regards,
Hervé
Le dimanche 22 janvier 2017, 16:41:44 CET Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 1 issue: we renamed Aether to Maven Artifact Resolver, with exact
> same code as Aether 1.0.2.
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1315/
> https://re
+1
On Sun 22 Jan 2017 at 15:42, Hervé BOUTEMY wrote:
> Hi,
>
>
>
> We solved 1 issue: we renamed Aether to Maven Artifact Resolver, with exact
>
> same code as Aether 1.0.2.
>
>
>
> Staging repo:
>
> https://repository.apache.org/content/repositories/maven-1315/
>
> https://repository.apache.org
+1
one remark: I've created MRESOLVER-16[1] which states that the license
should have a prominent spot on the site, especially since we're using the
org.eclipse.aether package namespace.
For now the website will be patched, next release it must be part of the
release.
thanks,
Robert
[1]
Hi,
sha1 checked Ok.
Tested on JDK 7, JDK 8 and JDK9+139
+1 from me..
The JDK9+139 build failed with the following message which is based on
the old versions of plexus-component-metadata (1.7.1 should fix this).
So no problem at the moment.
maven-parent version 30 will not fix this issue c
Hi,
We solved 1 issue: we renamed Aether to Maven Artifact Resolver, with exact
same code as Aether 1.0.2.
Staging repo:
https://repository.apache.org/content/repositories/maven-1315/
https://repository.apache.org/content/repositories/maven-1315/org/apache/
maven/resolver/maven-resolver/1.0.3/m
