[RESULT] [VOTE] Retire Maven OSGi
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 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-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Retire Maven OSGi
+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-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Retire Maven OSGi
+1 On Fri, Aug 23, 2019 at 3:17 PM 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: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Retire Maven OSGi
+1 Thank you Dirk for checking Enrico Il giorno ven 23 ago 2019 alle ore 20:48 Arnaud Héritier < aherit...@gmail.com> ha scritto: > +1 > > Le ven. 23 août 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: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > -- > - > Arnaud Héritier > http://aheritier.net > Mail/GTalk: aheritier AT gmail DOT com > Twitter/Skype : aheritier >
Re: [VOTE] Retire Maven OSGi
+1 Le ven. 23 août 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: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Retire Maven OSGi
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-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Retire Maven OSGi
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 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" > An: "Apache Maven Dev" > Cc: "Apache Maven Users" > 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-unsubscr...@maven.apache.org > >For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Retire Maven OSGi
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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Retire Maven OSGi
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" An: "Apache Maven Dev" Cc: "Apache Maven Users" 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-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Retire Maven OSGi
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 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-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Retire Maven OSGi
+1 /Anders (mobile) Den fre 23 aug. 2019 15:17Robert Scholte 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-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Retire Maven OSGi
+1 On Fri, Aug 23, 2019 at 3:17 PM 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: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
[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-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
