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/08/23 13:17:23 UTC
[VOTE] Retire Maven OSGi
Hi,
The Apache Maven project consist of about 90 (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.
https://maven.apache.org/shared/maven-osgi/ describes the main purpose in
one line: Library for Maven-OSGi integration.
There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
It is unclear to me if this library is still used. The library is based on
just 3 files: interface, default implementation and dedicated exception.
Either the library is complete or never used anymore. In both cases I see
no real reason to maintain it.
I therefore propose that we retire the maven-osgi library.
I don't think it makes sense to do a final release. Instead we should
update the documentation and 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] Retire Maven OSGi
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi,
+1 from me.
Kind regards
Karl Heinz Marbaise
On 23.08.19 15:17, Robert Scholte wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in
> December 2007 and just one open issue by Stuart McCulloch regarding an
> unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I
> see no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Retire Maven OSGi
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi,
+1 from me.
Kind regards
Karl Heinz Marbaise
On 23.08.19 15:17, Robert Scholte wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in
> December 2007 and just one open issue by Stuart McCulloch regarding an
> unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I
> see no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [VOTE] Retire Maven OSGi
Posted by Tibor Digana <ti...@apache.org>.
There's very good BND plugin org.apache.felix:maven-bundle-plugin.
+1 to retire and delete old https://maven.apache.org/shared/maven-osgi/
Cheers
Tibor17
On Fri, Aug 23, 2019 at 3:17 PM Robert Scholte <rf...@apache.org> wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in
> one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on
> just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I see
> no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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] Retire Maven OSGi
Posted by Tamás Cservenák <ta...@cservenak.net>.
+1
On Fri, Aug 23, 2019 at 3:17 PM Robert Scholte <rf...@apache.org> wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in
> one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on
> just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I see
> no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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] Retire Maven OSGi
Posted by Stephane Nicoll <st...@gmail.com>.
+1
On Fri, Aug 23, 2019 at 3:17 PM Robert Scholte <rf...@apache.org> wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in
> one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on
> just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I see
> no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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
>
>
[RESULT] [VOTE] Retire Maven OSGi
Posted by Robert Scholte <rf...@apache.org>.
Hi,
The vote has passed with the following result:
+1: Tamás Cservenák, Anders Hammar, Tibor Digana, Karl Heinz Marbaise,
Michael Osipov, Arnaud Héritier, Enrico Olivelli, Stephane Nicoll,
Francois Papon, Hervé BOUTEMY
PMC quorum: reached
Special thanks to Dirk Mahler for collecting a list of projects still
using the library.
I considered doing a final release anyway because of the provided
information, but after having a view on the list of commits on the project
and concluded it is still not worth it.
I will continue with the steps required to retire this library.
On Fri, 23 Aug 2019 15:17:23 +0200, Robert Scholte <rf...@apache.org>
wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in
> December 2007 and just one open issue by Stuart McCulloch regarding an
> unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on just 3 files: interface, default implementation and dedicated
> exception.
> Either the library is complete or never used anymore. In both cases I
> see no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Retire Maven OSGi
Posted by Anders Hammar <an...@hammar.net>.
+1
/Anders (mobile)
Den fre 23 aug. 2019 15:17Robert Scholte <rf...@apache.org> skrev:
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in
> one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on
> just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I see
> no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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] Retire Maven OSGi
Posted by Konrad Windszus <kw...@apache.org>.
Hi, just for the record:
There is a replacement for most of the classes in bnd: https://github.com/bndtools/bnd/blob/9a4d7bcc04c2377641911b517ca8b1915f763a9a/biz.aQute.bndlib/src/aQute/bnd/version/MavenVersion.java
I just replaced the code using maven-osgi with bndlib in Apache Sling : https://issues.apache.org/jira/browse/SLING-8656.
Konrad
On 2019/08/23 17:43:53, Tibor Digana <ti...@apache.org> wrote:
> Hi Dirk,
>
> This project is not worth a plugin, it is a pure converter of single class.
> In this case it is legal to adopt this code according to the license.
> Anyway the Maven is not the OSGi. The OSGi is not our key API we deliver to
> our customers.
> We have to save our energy on what makes Maven The Maven.
>
> Cheers
> Tibor17
>
> On Fri, Aug 23, 2019 at 5:21 PM Dirk Mahler <di...@buschmais.com>
> wrote:
>
> > Hi,
> >
> > I'm not using it but just for curiosity I checked on Maven Central if
> > some artifacts have been pushed there recently that declare a dependency
> > to this artifact (maven-osgi):
> >
> > "0.2.0" "org.glassfish.hk2:consolidatedbundle-maven-plugin:pom:2.6.0"
> > "2019-07-31T22:22:29Z"
> > "0.2.0" "org.glassfish.hk2:osgiversion-maven-plugin:pom:2.6.0"
> > "2019-07-31T22:21:55Z"
> > "0.2.0" "org.apache.sling:slingstart-maven-plugin:pom:1.8.4"
> > "2019-06-13T11:29:18Z"
> > "0.2.0" "org.apache.sling:slingfeature-maven-plugin:pom:1.0.4"
> > "2019-06-13T09:52:03Z"
> > ...
> >
> > Hope it helps for voting.
> >
> > Cheers
> >
> > Dirk
> >
> > ------ Originalnachricht ------
> > Von: "Robert Scholte" <rf...@apache.org>
> > An: "Apache Maven Dev" <de...@maven.apache.org>
> > Cc: "Apache Maven Users" <us...@maven.apache.org>
> > Gesendet: 23.08.2019 15:17:23
> > Betreff: [VOTE] Retire Maven OSGi
> >
> > >Hi,
> > >
> > >The Apache Maven project consist of about 90 (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.
> > >
> > >https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> > in one line: Library for Maven-OSGi integration.
> > >There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in
> > December 2007 and just one open issue by Stuart McCulloch regarding an
> > unclosed jar.
> > >It is unclear to me if this library is still used. The library is based
> > on just 3 files: interface, default implementation and dedicated exception.
> > >Either the library is complete or never used anymore. In both cases I
> > see no real reason to maintain it.
> > >
> > >I therefore propose that we retire the maven-osgi library.
> > >
> > >I don't think it makes sense to do a final release. Instead we should
> > update the documentation and 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
> > >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [VOTE] Retire Maven OSGi
Posted by Tibor Digana <ti...@apache.org>.
Hi Dirk,
This project is not worth a plugin, it is a pure converter of single class.
In this case it is legal to adopt this code according to the license.
Anyway the Maven is not the OSGi. The OSGi is not our key API we deliver to
our customers.
We have to save our energy on what makes Maven The Maven.
Cheers
Tibor17
On Fri, Aug 23, 2019 at 5:21 PM Dirk Mahler <di...@buschmais.com>
wrote:
> Hi,
>
> I'm not using it but just for curiosity I checked on Maven Central if
> some artifacts have been pushed there recently that declare a dependency
> to this artifact (maven-osgi):
>
> "0.2.0" "org.glassfish.hk2:consolidatedbundle-maven-plugin:pom:2.6.0"
> "2019-07-31T22:22:29Z"
> "0.2.0" "org.glassfish.hk2:osgiversion-maven-plugin:pom:2.6.0"
> "2019-07-31T22:21:55Z"
> "0.2.0" "org.apache.sling:slingstart-maven-plugin:pom:1.8.4"
> "2019-06-13T11:29:18Z"
> "0.2.0" "org.apache.sling:slingfeature-maven-plugin:pom:1.0.4"
> "2019-06-13T09:52:03Z"
> ...
>
> Hope it helps for voting.
>
> Cheers
>
> Dirk
>
> ------ Originalnachricht ------
> Von: "Robert Scholte" <rf...@apache.org>
> An: "Apache Maven Dev" <de...@maven.apache.org>
> Cc: "Apache Maven Users" <us...@maven.apache.org>
> Gesendet: 23.08.2019 15:17:23
> Betreff: [VOTE] Retire Maven OSGi
>
> >Hi,
> >
> >The Apache Maven project consist of about 90 (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.
> >
> >https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in one line: Library for Maven-OSGi integration.
> >There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in
> December 2007 and just one open issue by Stuart McCulloch regarding an
> unclosed jar.
> >It is unclear to me if this library is still used. The library is based
> on just 3 files: interface, default implementation and dedicated exception.
> >Either the library is complete or never used anymore. In both cases I
> see no real reason to maintain it.
> >
> >I therefore propose that we retire the maven-osgi library.
> >
> >I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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] Retire Maven OSGi
Posted by Tibor Digana <ti...@apache.org>.
Hi Dirk,
This project is not worth a plugin, it is a pure converter of single class.
In this case it is legal to adopt this code according to the license.
Anyway the Maven is not the OSGi. The OSGi is not our key API we deliver to
our customers.
We have to save our energy on what makes Maven The Maven.
Cheers
Tibor17
On Fri, Aug 23, 2019 at 5:21 PM Dirk Mahler <di...@buschmais.com>
wrote:
> Hi,
>
> I'm not using it but just for curiosity I checked on Maven Central if
> some artifacts have been pushed there recently that declare a dependency
> to this artifact (maven-osgi):
>
> "0.2.0" "org.glassfish.hk2:consolidatedbundle-maven-plugin:pom:2.6.0"
> "2019-07-31T22:22:29Z"
> "0.2.0" "org.glassfish.hk2:osgiversion-maven-plugin:pom:2.6.0"
> "2019-07-31T22:21:55Z"
> "0.2.0" "org.apache.sling:slingstart-maven-plugin:pom:1.8.4"
> "2019-06-13T11:29:18Z"
> "0.2.0" "org.apache.sling:slingfeature-maven-plugin:pom:1.0.4"
> "2019-06-13T09:52:03Z"
> ...
>
> Hope it helps for voting.
>
> Cheers
>
> Dirk
>
> ------ Originalnachricht ------
> Von: "Robert Scholte" <rf...@apache.org>
> An: "Apache Maven Dev" <de...@maven.apache.org>
> Cc: "Apache Maven Users" <us...@maven.apache.org>
> Gesendet: 23.08.2019 15:17:23
> Betreff: [VOTE] Retire Maven OSGi
>
> >Hi,
> >
> >The Apache Maven project consist of about 90 (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.
> >
> >https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in one line: Library for Maven-OSGi integration.
> >There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in
> December 2007 and just one open issue by Stuart McCulloch regarding an
> unclosed jar.
> >It is unclear to me if this library is still used. The library is based
> on just 3 files: interface, default implementation and dedicated exception.
> >Either the library is complete or never used anymore. In both cases I
> see no real reason to maintain it.
> >
> >I therefore propose that we retire the maven-osgi library.
> >
> >I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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] Retire Maven OSGi
Posted by Dirk Mahler <di...@buschmais.com>.
Hi,
I'm not using it but just for curiosity I checked on Maven Central if
some artifacts have been pushed there recently that declare a dependency
to this artifact (maven-osgi):
"0.2.0" "org.glassfish.hk2:consolidatedbundle-maven-plugin:pom:2.6.0"
"2019-07-31T22:22:29Z"
"0.2.0" "org.glassfish.hk2:osgiversion-maven-plugin:pom:2.6.0"
"2019-07-31T22:21:55Z"
"0.2.0" "org.apache.sling:slingstart-maven-plugin:pom:1.8.4"
"2019-06-13T11:29:18Z"
"0.2.0" "org.apache.sling:slingfeature-maven-plugin:pom:1.0.4"
"2019-06-13T09:52:03Z"
...
Hope it helps for voting.
Cheers
Dirk
------ Originalnachricht ------
Von: "Robert Scholte" <rf...@apache.org>
An: "Apache Maven Dev" <de...@maven.apache.org>
Cc: "Apache Maven Users" <us...@maven.apache.org>
Gesendet: 23.08.2019 15:17:23
Betreff: [VOTE] Retire Maven OSGi
>Hi,
>
>The Apache Maven project consist of about 90 (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.
>
>https://maven.apache.org/shared/maven-osgi/ describes the main purpose in one line: Library for Maven-OSGi integration.
>There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
>It is unclear to me if this library is still used. The library is based on just 3 files: interface, default implementation and dedicated exception.
>Either the library is complete or never used anymore. In both cases I see no real reason to maintain it.
>
>I therefore propose that we retire the maven-osgi library.
>
>I don't think it makes sense to do a final release. Instead we should update the documentation and 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] Retire Maven OSGi
Posted by Tibor Digana <ti...@apache.org>.
There's very good BND plugin org.apache.felix:maven-bundle-plugin.
+1 to retire and delete old https://maven.apache.org/shared/maven-osgi/
Cheers
Tibor17
On Fri, Aug 23, 2019 at 3:17 PM Robert Scholte <rf...@apache.org> wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in
> one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on
> just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I see
> no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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] Retire Maven OSGi
Posted by Tamás Cservenák <ta...@cservenak.net>.
+1
On Fri, Aug 23, 2019 at 3:17 PM Robert Scholte <rf...@apache.org> wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in
> one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on
> just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I see
> no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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] Retire Maven OSGi
Posted by Michael Osipov <mi...@apache.org>.
Am 2019-08-23 um 15:17 schrieb Robert Scholte:
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in
> December 2007 and just one open issue by Stuart McCulloch regarding an
> unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I
> see no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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]
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Retire Maven OSGi
Posted by Enrico Olivelli <eo...@gmail.com>.
+1
Thank you Dirk for checking
Enrico
Il giorno ven 23 ago 2019 alle ore 20:48 Arnaud Héritier <
aheritier@gmail.com> ha scritto:
> +1
>
> Le ven. 23 août 2019 à 15:17, Robert Scholte <rf...@apache.org> a
> écrit :
>
> > Hi,
> >
> > The Apache Maven project consist of about 90 (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.
> >
> > https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> > in
> > one line: Library for Maven-OSGi integration.
> > There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> > 2007 and just one open issue by Stuart McCulloch regarding an unclosed
> jar.
> > It is unclear to me if this library is still used. The library is based
> > on
> > just 3 files: interface, default implementation and dedicated exception.
> > Either the library is complete or never used anymore. In both cases I see
> > no real reason to maintain it.
> >
> > I therefore propose that we retire the maven-osgi library.
> >
> > I don't think it makes sense to do a final release. Instead we should
> > update the documentation and 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
> >
> > --
> -----
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>
Re: [VOTE] Retire Maven OSGi
Posted by Enrico Olivelli <eo...@gmail.com>.
+1
Thank you Dirk for checking
Enrico
Il giorno ven 23 ago 2019 alle ore 20:48 Arnaud Héritier <
aheritier@gmail.com> ha scritto:
> +1
>
> Le ven. 23 août 2019 à 15:17, Robert Scholte <rf...@apache.org> a
> écrit :
>
> > Hi,
> >
> > The Apache Maven project consist of about 90 (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.
> >
> > https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> > in
> > one line: Library for Maven-OSGi integration.
> > There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> > 2007 and just one open issue by Stuart McCulloch regarding an unclosed
> jar.
> > It is unclear to me if this library is still used. The library is based
> > on
> > just 3 files: interface, default implementation and dedicated exception.
> > Either the library is complete or never used anymore. In both cases I see
> > no real reason to maintain it.
> >
> > I therefore propose that we retire the maven-osgi library.
> >
> > I don't think it makes sense to do a final release. Instead we should
> > update the documentation and 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
> >
> > --
> -----
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>
Re: [VOTE] Retire Maven OSGi
Posted by Arnaud Héritier <ah...@gmail.com>.
+1
Le ven. 23 août 2019 à 15:17, Robert Scholte <rf...@apache.org> a
écrit :
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in
> one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on
> just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I see
> no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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
>
> --
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
Re: [VOTE] Retire Maven OSGi
Posted by Hervé BOUTEMY <he...@free.fr>.
+1
Regards,
Hervé
Le vendredi 23 août 2019, 15:17:23 CEST Robert Scholte a écrit :
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose in
> one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
> It is unclear to me if this library is still used. The library is based on
> just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I see
> no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[RESULT] [VOTE] Retire Maven OSGi
Posted by Robert Scholte <rf...@apache.org>.
Hi,
The vote has passed with the following result:
+1: Tamás Cservenák, Anders Hammar, Tibor Digana, Karl Heinz Marbaise,
Michael Osipov, Arnaud Héritier, Enrico Olivelli, Stephane Nicoll,
Francois Papon, Hervé BOUTEMY
PMC quorum: reached
Special thanks to Dirk Mahler for collecting a list of projects still
using the library.
I considered doing a final release anyway because of the provided
information, but after having a view on the list of commits on the project
and concluded it is still not worth it.
I will continue with the steps required to retire this library.
On Fri, 23 Aug 2019 15:17:23 +0200, Robert Scholte <rf...@apache.org>
wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in
> December 2007 and just one open issue by Stuart McCulloch regarding an
> unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on just 3 files: interface, default implementation and dedicated
> exception.
> Either the library is complete or never used anymore. In both cases I
> see no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [VOTE] Retire Maven OSGi
Posted by Arnaud Héritier <ah...@gmail.com>.
+1
Le ven. 23 août 2019 à 15:17, Robert Scholte <rf...@apache.org> a
écrit :
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in
> one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December
> 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar.
> It is unclear to me if this library is still used. The library is based
> on
> just 3 files: interface, default implementation and dedicated exception.
> Either the library is complete or never used anymore. In both cases I see
> no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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
>
> --
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
Re: [VOTE] Retire Maven OSGi
Posted by Francois Papon <fr...@openobject.fr>.
Yes, the maven-bundle-plugin from Apache Felix do the job :)
+1 (non-binding)
Thanks!
regards,
François
fpapon@apache.org
Le 23/08/2019 à 15:17, Robert Scholte a écrit :
> Hi,
>
> The Apache Maven project consist of about 90 (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.
>
> https://maven.apache.org/shared/maven-osgi/ describes the main purpose
> in one line: Library for Maven-OSGi integration.
> There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in
> December 2007 and just one open issue by Stuart McCulloch regarding an
> unclosed jar.
> It is unclear to me if this library is still used. The library is
> based on just 3 files: interface, default implementation and dedicated
> exception.
> Either the library is complete or never used anymore. In both cases I
> see no real reason to maintain it.
>
> I therefore propose that we retire the maven-osgi library.
>
> I don't think it makes sense to do a final release. Instead we should
> update the documentation and 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org