Re: [VOTE] Retire Maven Ant Plugin
+1 it's the right thing to do. On Thu, May 30, 2019 at 7:51 AM Gabriel Belingueres wrote: > +1 > > Regards > Gabriel > > El mar., 28 de may. de 2019 15:54, Robert Scholte > 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 goal of the Apache Maven Ant Plugin it to generate Ant build files > > based on a pom.xml and was released for the last time in December 2014. > Due > > to the different ways that Ant and Maven work I don't think it makes > > sense anymore to maintain a plugin to transform Maven files to Ant. > > See https://maven.apache.org/plugins/maven-ant-plugin/ [ > > https://maven.apache.org/plugins/maven-ant-plugin/] > > > > To be clear, this is NOT the plugin you can use to run Ant within Maven; > > that's the maven-antrun-plugin. > > > > I therefore propose that we retire the maven-ant-plugin. > > > > 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 > > > > The vote is open for 72 hours. > > [ ] +1 Yes, it's about time > > [ ] -1 No, because... >
Re: [VOTE] Retire Maven Ant Plugin
+1 Regards Gabriel El mar., 28 de may. de 2019 15:54, Robert Scholte 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 goal of the Apache Maven Ant Plugin it to generate Ant build files > based on a pom.xml and was released for the last time in December 2014. Due > to the different ways that Ant and Maven work I don't think it makes > sense anymore to maintain a plugin to transform Maven files to Ant. > See https://maven.apache.org/plugins/maven-ant-plugin/ [ > https://maven.apache.org/plugins/maven-ant-plugin/] > > To be clear, this is NOT the plugin you can use to run Ant within Maven; > that's the maven-antrun-plugin. > > I therefore propose that we retire the maven-ant-plugin. > > 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 > > The vote is open for 72 hours. > [ ] +1 Yes, it's about time > [ ] -1 No, because...
Re: [VOTE] Retire Maven Ant Plugin
+1 On Tue, 28 May 2019 at 19:54, 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 goal of the Apache Maven Ant Plugin it to generate Ant build files > based on a pom.xml and was released for the last time in December 2014. Due > to the different ways that Ant and Maven work I don't think it makes > sense anymore to maintain a plugin to transform Maven files to Ant. > See https://maven.apache.org/plugins/maven-ant-plugin/ [ > https://maven.apache.org/plugins/maven-ant-plugin/] > > To be clear, this is NOT the plugin you can use to run Ant within Maven; > that's the maven-antrun-plugin. > > I therefore propose that we retire the maven-ant-plugin. > > 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 > > The vote is open for 72 hours. > [ ] +1 Yes, it's about time > [ ] -1 No, because...
Re: [VOTE] Retire Maven Ant Plugin
+1 On Tue 28 May 2019 at 19:54, 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 goal of the Apache Maven Ant Plugin it to generate Ant build files > based on a pom.xml and was released for the last time in December 2014. Due > to the different ways that Ant and Maven work I don't think it makes > sense anymore to maintain a plugin to transform Maven files to Ant. > See https://maven.apache.org/plugins/maven-ant-plugin/ [ > https://maven.apache.org/plugins/maven-ant-plugin/] > > To be clear, this is NOT the plugin you can use to run Ant within Maven; > that's the maven-antrun-plugin. > > I therefore propose that we retire the maven-ant-plugin. > > 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 > > The vote is open for 72 hours. > [ ] +1 Yes, it's about time > [ ] -1 No, because... -- Sent from my phone
[GitHub] [maven-doxia] harawata commented on issue #17: [DOXIA-583] Avoid over-escaping table captions
harawata commented on issue #17: [DOXIA-583] Avoid over-escaping table captions URL: https://github.com/apache/maven-doxia/pull/17#issuecomment-496942515 Updated. Please let me know if there is anything you want me to change. Thanks again for your time! =) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-doxia] slachiewicz commented on issue #17: [DOXIA-583] Avoid over-escaping table captions
slachiewicz commented on issue #17: [DOXIA-583] Avoid over-escaping table captions URL: https://github.com/apache/maven-doxia/pull/17#issuecomment-496932864 looks good to me. Please squash commits related to table caption to one and separate only related to .contains. Thx for time spent on verification! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-doxia] harawata commented on issue #17: [DOXIA-583] Avoid over-escaping table captions
harawata commented on issue #17: [DOXIA-583] Avoid over-escaping table captions URL: https://github.com/apache/maven-doxia/pull/17#issuecomment-496907294 Hi again, As I mentioned, the 'expected value' of the assertions had to be modified to pass the tests after replacing `indexOf(...) != 1` with `contains()`. Does the commit c8e834b649f7f7d5ee2b51c0f210c20c8e9bebdd look OK to you? Or could it be related to [DOXIA-588](https://issues.apache.org/jira/projects/DOXIA/issues/DOXIA-588) maybe? If it looks OK to you, please let me know and I'll do the squash & force-push. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-doxia] asfgit merged pull request #9: [DOXIA-570] Escape links to xml based figureGraphics image elements
asfgit merged pull request #9: [DOXIA-570] Escape links to xml based figureGraphics image elements URL: https://github.com/apache/maven-doxia/pull/9 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Latest snapshot build (archive, not Maven artifact)
I think an infra that wants to prevent adopters for giving feedback on snapshots is harmful for an open-source project. Are alternatives like Sonatype OSSRH considered for replacement?
Re: Latest snapshot build (archive, not Maven artifact)
not sure as infra wants to avoid too much usage of r.a.o so we will avoid noise On Wed, 29 May 2019 at 17:00, Mickael Istria wrote: > Thanks a lot! > I think it would be worth a dedicated announce post on the mailing-list or > other community channels (blog, twitter...). > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Latest snapshot build (archive, not Maven artifact)
Concretely, m2e can now pretty easily test against Maven snapshot: https://git.eclipse.org/r/142991 . This should allow m2e to detect and report Maven issues sooner, and to adopt newer Maven shortly after release as we can span integration effort all along the development phase instead of starting it after the release. It's really a kind of revolution for m2e and Maven collaboration!
Re: Latest snapshot build (archive, not Maven artifact)
Thanks a lot! I think it would be worth a dedicated announce post on the mailing-list or other community channels (blog, twitter...).
