Re: [VOTE] Retired Maven Artifact Resolution API (Maven2)

2019-05-09 Thread Guang Chao 
+1

On Thu, May 9, 2019 at 2:32 PM Bernd Prager  wrote:

> +1
>
> On 9/5/62 01:25, Robert Scholte wrote:
> > Hi,
> >
> > The Apache Maven project consist of about 100 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects, including
> our ambitious ideas for the next major version(s) of Maven itself.
> > To be able to gain more focus we need to criticize the current
> subprojects and decide if it is worth maintaining.
> >
> > The Maven Artifact Resolution API (maven-artifact-resolver) is a shared
> component that could be used to easily resolve Maven project dependencies.
> The last (and only) released version is 1.0 in September 2009.(
> https://maven.apache.org/shared/maven-artifact-resolver/ [
> https://maven.apache.org/shared/maven-artifact-resolver/] ).
> > This library should not be confused with Artifact Resolver
> (maven-resolver), previously known as Aether. As you can see the naming
> will cause confusion.
> > The library that aims the same goal for Artifact Resolver is another
> shared component called maven-artifact-transfer (which by now is not just
> the transfer part or Artifact Resolver, but a bridge for both Sonatype
> Aether as used in Maven 3.0.x and Eclipse Aether as used in Maven 3.1.x+.
> This way Maven plugins and extensions can be compatible with any Maven 3
> release)
> >
> > I therefore propose that we retire the maven-artifact-resolver.
> >
> > I don't think it makes sense to do a final release. Instead we should
> update the documentation and the freeze the codebase.
> >
> > The process for retiring a plugin is described here:
> > https://maven.apache.org/developers/retirement-plan-plugins.html [
> https://maven.apache.org/developers/retirement-plan-plugins.html]
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Yes, it's about time
> > [ ] -1 No, because...
> --
> Bernd Prager
>
> Mobile: +66.91.770.5758
> Skype: bernd.pra...@outlook.com
> PGP Public
> Key: https://pgp.mit.edu/pks/lookup?op=get&search=0xBDA6C225628DB3CD
> PGP Fingerprint: 0AA3 952C F211 E98A CD18 9E55 BDA6 C225 628D B3CD
>
>
>
>


-- 
Guang

Re: [VOTE] Retired Maven Artifact Resolution API (Maven2)

2019-05-09 Thread Enrico Olivelli 
+1

Enrico

Il gio 9 mag 2019, 08:32 Bernd Prager  ha scritto:

> +1
>
> On 9/5/62 01:25, Robert Scholte wrote:
> > Hi,
> >
> > The Apache Maven project consist of about 100 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects, including
> our ambitious ideas for the next major version(s) of Maven itself.
> > To be able to gain more focus we need to criticize the current
> subprojects and decide if it is worth maintaining.
> >
> > The Maven Artifact Resolution API (maven-artifact-resolver) is a shared
> component that could be used to easily resolve Maven project dependencies.
> The last (and only) released version is 1.0 in September 2009.(
> https://maven.apache.org/shared/maven-artifact-resolver/ [
> https://maven.apache.org/shared/maven-artifact-resolver/] ).
> > This library should not be confused with Artifact Resolver
> (maven-resolver), previously known as Aether. As you can see the naming
> will cause confusion.
> > The library that aims the same goal for Artifact Resolver is another
> shared component called maven-artifact-transfer (which by now is not just
> the transfer part or Artifact Resolver, but a bridge for both Sonatype
> Aether as used in Maven 3.0.x and Eclipse Aether as used in Maven 3.1.x+.
> This way Maven plugins and extensions can be compatible with any Maven 3
> release)
> >
> > I therefore propose that we retire the maven-artifact-resolver.
> >
> > I don't think it makes sense to do a final release. Instead we should
> update the documentation and the freeze the codebase.
> >
> > The process for retiring a plugin is described here:
> > https://maven.apache.org/developers/retirement-plan-plugins.html [
> https://maven.apache.org/developers/retirement-plan-plugins.html]
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Yes, it's about time
> > [ ] -1 No, because...
> --
> Bernd Prager
>
> Mobile: +66.91.770.5758
> Skype: bernd.pra...@outlook.com
> PGP Public
> Key: https://pgp.mit.edu/pks/lookup?op=get&search=0xBDA6C225628DB3CD
> PGP Fingerprint: 0AA3 952C F211 E98A CD18 9E55 BDA6 C225 628D B3CD
>
>
>
>

Re: [VOTE] Retired Maven Artifact Resolution API (Maven2)

2019-05-08 Thread Bernd Prager 
+1

On 9/5/62 01:25, Robert Scholte wrote:
> Hi,
>
> The Apache Maven project consist of about 100 (sub)projects. Due to the small 
> number of volunteers and the huge amount of code to maintain we're missing 
> enough space to make real progress on all these projects, including our 
> ambitious ideas for the next major version(s) of Maven itself.
> To be able to gain more focus we need to criticize the current subprojects 
> and decide if it is worth maintaining.
>
> The Maven Artifact Resolution API (maven-artifact-resolver) is a shared 
> component that could be used to easily resolve Maven project dependencies. 
> The last (and only) released version is 1.0 in September 2009.( 
> https://maven.apache.org/shared/maven-artifact-resolver/ 
> [https://maven.apache.org/shared/maven-artifact-resolver/] ).
> This library should not be confused with Artifact Resolver (maven-resolver), 
> previously known as Aether. As you can see the naming will cause confusion.
> The library that aims the same goal for Artifact Resolver is another shared 
> component called maven-artifact-transfer (which by now is not just the 
> transfer part or Artifact Resolver, but a bridge for both Sonatype Aether as 
> used in Maven 3.0.x and Eclipse Aether as used in Maven 3.1.x+. This way 
> Maven plugins and extensions can be compatible with any Maven 3 release)
>
> I therefore propose that we retire the maven-artifact-resolver.
>
> I don't think it makes sense to do a final release. Instead we should update 
> the documentation and the freeze the codebase.
>
> The process for retiring a plugin is described here:
> https://maven.apache.org/developers/retirement-plan-plugins.html 
> [https://maven.apache.org/developers/retirement-plan-plugins.html]
>
> The vote is open for 72 hours.
>
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...
-- 
Bernd Prager
 
Mobile: +66.91.770.5758 
Skype: bernd.pra...@outlook.com 
PGP Public
Key: https://pgp.mit.edu/pks/lookup?op=get&search=0xBDA6C225628DB3CD 
PGP Fingerprint: 0AA3 952C F211 E98A CD18 9E55 BDA6 C225 628D B3CD 
 

 

Re: [VOTE] Retired Maven Artifact Resolution API (Maven2)

2019-05-08 Thread Manfred Moser 
+1 

Robert Scholte wrote on 2019-05-08 11:25:

> Hi,
> 
> The Apache Maven project consist of about 100 (sub)projects. Due to the small
> number of volunteers and the huge amount of code to maintain we're missing
> enough space to make real progress on all these projects, including
> our ambitious ideas for the next major version(s) of Maven itself.
> To be able to gain more focus we need to criticize the current subprojects and
> decide if it is worth maintaining.
> 
> The Maven Artifact Resolution API (maven-artifact-resolver) is a shared
> component that could be used to easily resolve Maven project dependencies. The
> last (and only) released version is 1.0 in September
> 2009.( https://maven.apache.org/shared/maven-artifact-resolver/
> [https://maven.apache.org/shared/maven-artifact-resolver/] ).
> This library should not be confused with Artifact Resolver (maven-resolver),
> previously known as Aether. As you can see the naming will cause confusion.
> The library that aims the same goal for Artifact Resolver is another shared
> component called maven-artifact-transfer (which by now is not just the 
> transfer
> part or Artifact Resolver, but a bridge for both Sonatype Aether as used in
> Maven 3.0.x and Eclipse Aether as used in Maven 3.1.x+. This way Maven plugins
> and extensions can be compatible with any Maven 3 release)
> 
> I therefore propose that we retire the maven-artifact-resolver.
> 
> I don't think it makes sense to do a final release. Instead we should update
> the documentation and the freeze the codebase.
> 
> The process for retiring a plugin is described here:
> https://maven.apache.org/developers/retirement-plan-plugins.html
> [https://maven.apache.org/developers/retirement-plan-plugins.html]
> 
> The vote is open for 72 hours.
> 
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...


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

Re: [VOTE] Retired Maven Artifact Resolution API (Maven2)

2019-05-08 Thread Anders Hammar 
+1

/Anders (mobile)

Den ons 8 maj 2019 20:25Robert Scholte  skrev:

> Hi,
>
> The Apache Maven project consist of about 100 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects, including
> our ambitious ideas for the next major version(s) of Maven itself.
> To be able to gain more focus we need to criticize the current subprojects
> and decide if it is worth maintaining.
>
> The Maven Artifact Resolution API (maven-artifact-resolver) is a shared
> component that could be used to easily resolve Maven project dependencies.
> The last (and only) released version is 1.0 in September 2009.(
> https://maven.apache.org/shared/maven-artifact-resolver/ [
> https://maven.apache.org/shared/maven-artifact-resolver/] ).
> This library should not be confused with Artifact Resolver
> (maven-resolver), previously known as Aether. As you can see the naming
> will cause confusion.
> The library that aims the same goal for Artifact Resolver is another
> shared component called maven-artifact-transfer (which by now is not just
> the transfer part or Artifact Resolver, but a bridge for both Sonatype
> Aether as used in Maven 3.0.x and Eclipse Aether as used in Maven 3.1.x+.
> This way Maven plugins and extensions can be compatible with any Maven 3
> release)
>
> I therefore propose that we retire the maven-artifact-resolver.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and the freeze the codebase.
>
> The process for retiring a plugin is described here:
> https://maven.apache.org/developers/retirement-plan-plugins.html [
> https://maven.apache.org/developers/retirement-plan-plugins.html]
>
> The vote is open for 72 hours.
>
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...

Re: [VOTE] Retired Maven Artifact Resolution API (Maven2)

2019-05-08 Thread Karl Heinz Marbaise 

Hi,
+1 from me.

Kind regards
Karl Heinz Marbaise

On 08.05.19 20:25, Robert Scholte wrote:

Hi,

The Apache Maven project consist of about 100 (sub)projects. Due to the small 
number of volunteers and the huge amount of code to maintain we're missing 
enough space to make real progress on all these projects, including our 
ambitious ideas for the next major version(s) of Maven itself.
To be able to gain more focus we need to criticize the current subprojects and 
decide if it is worth maintaining.

The Maven Artifact Resolution API (maven-artifact-resolver) is a shared 
component that could be used to easily resolve Maven project dependencies. The 
last (and only) released version is 1.0 in September 2009.( 
https://maven.apache.org/shared/maven-artifact-resolver/ 
[https://maven.apache.org/shared/maven-artifact-resolver/] ).
This library should not be confused with Artifact Resolver (maven-resolver), 
previously known as Aether. As you can see the naming will cause confusion.
The library that aims the same goal for Artifact Resolver is another shared 
component called maven-artifact-transfer (which by now is not just the transfer 
part or Artifact Resolver, but a bridge for both Sonatype Aether as used in 
Maven 3.0.x and Eclipse Aether as used in Maven 3.1.x+. This way Maven plugins 
and extensions can be compatible with any Maven 3 release)

I therefore propose that we retire the maven-artifact-resolver.

I don't think it makes sense to do a final release. Instead we should update 
the documentation and the freeze the codebase.

The process for retiring a plugin is described here:
https://maven.apache.org/developers/retirement-plan-plugins.html 
[https://maven.apache.org/developers/retirement-plan-plugins.html]

The vote is open for 72 hours.

[ ] +1 Yes, it's about time
[ ] -1 No, because...



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

[VOTE] Retired Maven Artifact Resolution API (Maven2)

2019-05-08 Thread Robert Scholte 
Hi,

The Apache Maven project consist of about 100 (sub)projects. Due to the small 
number of volunteers and the huge amount of code to maintain we're missing 
enough space to make real progress on all these projects, including our 
ambitious ideas for the next major version(s) of Maven itself.
To be able to gain more focus we need to criticize the current subprojects and 
decide if it is worth maintaining.

The Maven Artifact Resolution API (maven-artifact-resolver) is a shared 
component that could be used to easily resolve Maven project dependencies. The 
last (and only) released version is 1.0 in September 2009.( 
https://maven.apache.org/shared/maven-artifact-resolver/ 
[https://maven.apache.org/shared/maven-artifact-resolver/] ).
This library should not be confused with Artifact Resolver (maven-resolver), 
previously known as Aether. As you can see the naming will cause confusion.
The library that aims the same goal for Artifact Resolver is another shared 
component called maven-artifact-transfer (which by now is not just the transfer 
part or Artifact Resolver, but a bridge for both Sonatype Aether as used in 
Maven 3.0.x and Eclipse Aether as used in Maven 3.1.x+. This way Maven plugins 
and extensions can be compatible with any Maven 3 release)

I therefore propose that we retire the maven-artifact-resolver.

I don't think it makes sense to do a final release. Instead we should update 
the documentation and the freeze the codebase.

The process for retiring a plugin is described here:
https://maven.apache.org/developers/retirement-plan-plugins.html 
[https://maven.apache.org/developers/retirement-plan-plugins.html]

The vote is open for 72 hours.

[ ] +1 Yes, it's about time
[ ] -1 No, because...