Re: [jelly] Site build and Jellydoc plugin
>The PR is about 1.5 weeks old, so we should still give him some more time. +1 >Do you know him in person, Bruno? Or did you have contact with him in the past? He helped me to organize the Brazilian Jenkins mailing list, and the two first conferences in Brazil. He flew there to help organize and give keynote presentations too. One of the most intelligent and humble programmers I had a chance to chat in person. Bruno From: Oliver Heger <oliver.he...@oliver-heger.de> To: dev@commons.apache.org Sent: Monday, 6 November 2017 4:55 AM Subject: Re: [jelly] Site build and Jellydoc plugin Am 02.11.2017 um 00:33 schrieb Bruno P. Kinoshita: > I think it may be worth to try to get in touch with Kohsuke. He became the > CTO of CloudBees some time ago, but is still involved in the project (not > writing as much code as before) mainly with decisions, and eventual pull > request review. > You can find him sometimes on IRC / FreeNode, in the jenkins channel. But > given how busy he might be, probably dropping him an e-mail and waiting a bit > more might be a better idea. > > Hope that helpsBruno The PR is about 1.5 weeks old, so we should still give him some more time. Do you know him in person, Bruno? Or did you have contact with him in the past? Thanks Oliver > > From: Oliver Heger <oliver.he...@oliver-heger.de> > To: Commons Developers List <dev@commons.apache.org> > Sent: Thursday, 2 November 2017 9:34 AM > Subject: [jelly] Site build and Jellydoc plugin > > Hi, > > recently I did some work to get the Jelly site build with Maven running. > As this is experimental, I created my own fork of the project for this > purpose [1]. > > An important part of the documentation is the Jellydoc, an automatically > generated documentation for the standard tag libs shipped with Jelly. > This documentation is generated by the maven-jellydoc-plugin [2]. > Unfortunately, the plugin has a few bugs which cause the site build to fail. > > I therefore created a pull request [3] that fixes these problems. With > the patched version the build is now successful. > > However, there has not yet been a reaction on this PR. Given the fact > that the plugin code had not been touched for more than 6 years, it may > well be possible that Kohsuke Kawaguchi, the author of the plugin, is no > longer interested in this code base. > > Any thoughts how we could proceed here? > > Oliver > > [1] https://github.com/oheger/commons-jelly/tree/siteBuild > [2] https://github.com/kohsuke/maven-jellydoc-plugin > [3] https://github.com/kohsuke/maven-jellydoc-plugin/pull/1 > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [jelly] Site build and Jellydoc plugin
Am 02.11.2017 um 00:33 schrieb Bruno P. Kinoshita: > I think it may be worth to try to get in touch with Kohsuke. He became the > CTO of CloudBees some time ago, but is still involved in the project (not > writing as much code as before) mainly with decisions, and eventual pull > request review. > You can find him sometimes on IRC / FreeNode, in the jenkins channel. But > given how busy he might be, probably dropping him an e-mail and waiting a bit > more might be a better idea. > > Hope that helpsBruno The PR is about 1.5 weeks old, so we should still give him some more time. Do you know him in person, Bruno? Or did you have contact with him in the past? Thanks Oliver > > From: Oliver Heger <oliver.he...@oliver-heger.de> > To: Commons Developers List <dev@commons.apache.org> > Sent: Thursday, 2 November 2017 9:34 AM > Subject: [jelly] Site build and Jellydoc plugin > > Hi, > > recently I did some work to get the Jelly site build with Maven running. > As this is experimental, I created my own fork of the project for this > purpose [1]. > > An important part of the documentation is the Jellydoc, an automatically > generated documentation for the standard tag libs shipped with Jelly. > This documentation is generated by the maven-jellydoc-plugin [2]. > Unfortunately, the plugin has a few bugs which cause the site build to fail. > > I therefore created a pull request [3] that fixes these problems. With > the patched version the build is now successful. > > However, there has not yet been a reaction on this PR. Given the fact > that the plugin code had not been touched for more than 6 years, it may > well be possible that Kohsuke Kawaguchi, the author of the plugin, is no > longer interested in this code base. > > Any thoughts how we could proceed here? > > Oliver > > [1] https://github.com/oheger/commons-jelly/tree/siteBuild > [2] https://github.com/kohsuke/maven-jellydoc-plugin > [3] https://github.com/kohsuke/maven-jellydoc-plugin/pull/1 > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [jelly] Site build and Jellydoc plugin
I think it may be worth to try to get in touch with Kohsuke. He became the CTO of CloudBees some time ago, but is still involved in the project (not writing as much code as before) mainly with decisions, and eventual pull request review. You can find him sometimes on IRC / FreeNode, in the jenkins channel. But given how busy he might be, probably dropping him an e-mail and waiting a bit more might be a better idea. Hope that helpsBruno From: Oliver Heger <oliver.he...@oliver-heger.de> To: Commons Developers List <dev@commons.apache.org> Sent: Thursday, 2 November 2017 9:34 AM Subject: [jelly] Site build and Jellydoc plugin Hi, recently I did some work to get the Jelly site build with Maven running. As this is experimental, I created my own fork of the project for this purpose [1]. An important part of the documentation is the Jellydoc, an automatically generated documentation for the standard tag libs shipped with Jelly. This documentation is generated by the maven-jellydoc-plugin [2]. Unfortunately, the plugin has a few bugs which cause the site build to fail. I therefore created a pull request [3] that fixes these problems. With the patched version the build is now successful. However, there has not yet been a reaction on this PR. Given the fact that the plugin code had not been touched for more than 6 years, it may well be possible that Kohsuke Kawaguchi, the author of the plugin, is no longer interested in this code base. Any thoughts how we could proceed here? Oliver [1] https://github.com/oheger/commons-jelly/tree/siteBuild [2] https://github.com/kohsuke/maven-jellydoc-plugin [3] https://github.com/kohsuke/maven-jellydoc-plugin/pull/1 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[jelly] Site build and Jellydoc plugin
Hi, recently I did some work to get the Jelly site build with Maven running. As this is experimental, I created my own fork of the project for this purpose [1]. An important part of the documentation is the Jellydoc, an automatically generated documentation for the standard tag libs shipped with Jelly. This documentation is generated by the maven-jellydoc-plugin [2]. Unfortunately, the plugin has a few bugs which cause the site build to fail. I therefore created a pull request [3] that fixes these problems. With the patched version the build is now successful. However, there has not yet been a reaction on this PR. Given the fact that the plugin code had not been touched for more than 6 years, it may well be possible that Kohsuke Kawaguchi, the author of the plugin, is no longer interested in this code base. Any thoughts how we could proceed here? Oliver [1] https://github.com/oheger/commons-jelly/tree/siteBuild [2] https://github.com/kohsuke/maven-jellydoc-plugin [3] https://github.com/kohsuke/maven-jellydoc-plugin/pull/1 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
