You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@maven.apache.org by Robert Scholte <rf...@apache.org> on 2019/05/08 18:25:14 UTC

[VOTE] Retired Maven Artifact Resolution API (Maven2)

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...

[RESULT] [VOTE] Retired Maven Artifact Resolution API (Maven2)

Posted by Robert Scholte <rf...@apache.org>.

Hi,

The vote has passed with the following result:

+1: Karl Heinz Marbaise, Anders Hammar, Hervé BOUTEMY, Tamás Cservenák, Gabriel Belingueres, Manfred Moser, Bernd Prager, Enrico Olivelli, Guang Chao, Tibor Digana, Sylwester Lachiewicz, Robert Scholte

PMC quorum: reached

I will continue with the steps required to retire this library.

On 8-5-2019 20:25:14, Robert Scholte <rf...@apache.org> wrote:
Hi,

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)

Posted by Robert Scholte <rf...@apache.org>.

+1
On 8-5-2019 20:25:14, Robert Scholte <rf...@apache.org> wrote:
Hi,

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)

Posted by Anders Hammar <an...@hammar.net>.

+1

/Anders (mobile)

Den ons 8 maj 2019 20:25Robert Scholte <rf...@apache.org> 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)

Posted by Karl Heinz Marbaise <kh...@gmx.de>.

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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Karl Heinz Marbaise <kh...@gmx.de>.

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

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

Posted by Manfred Moser <ma...@simpligility.com>.

+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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

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

Posted by Anders Hammar <an...@hammar.net>.

+1

/Anders (mobile)

Den ons 8 maj 2019 20:25Robert Scholte <rf...@apache.org> 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)

Posted by Tamás Cservenák <ta...@cservenak.net>.

+1

T

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

Posted by Hervé BOUTEMY <he...@free.fr>.

+1

regards,

Hervé

Le mercredi 8 mai 2019, 20:25:14 CEST Robert Scholte a écrit :
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

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

Posted by Sylwester Lachiewicz <sl...@gmail.com>.

+1

W dniu sob., 11.05.2019 o 01:30 Tibor Digana <ti...@apache.org>
napisał(a):

> +1
>
> On Wed, May 8, 2019 at 8:25 PM Robert Scholte <rf...@apache.org>
> 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...
>

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

Posted by Tibor Digana <ti...@apache.org>.

+1

On Wed, May 8, 2019 at 8:25 PM Robert Scholte <rf...@apache.org> 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...

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

Posted by Gabriel Belingueres <be...@gmail.com>.

+1

Regards,
Gabriel

El mié., 8 de may. de 2019 a la(s) 15:25, Robert Scholte (
rfscholte@apache.org) escribió:

> 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)

Posted by Enrico Olivelli <eo...@gmail.com>.

+1

Enrico

Il gio 9 mag 2019, 08:32 Bernd Prager <be...@prager.ws> 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.prager@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)

Posted by Guang Chao <gu...@gmail.com>.

+1

On Thu, May 9, 2019 at 2:32 PM Bernd Prager <be...@prager.ws> 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.prager@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 <http://javadevnotes.com/fibonacci-java>

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

Posted by Bernd Prager <be...@prager.ws>.

+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.prager@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