Clover 3.1.x license is now available!!! was Re: svnpubsub misery (dropping Maven Clover reports)
On Tue, 2013-01-15 at 16:26 +, sebb wrote: On 15 January 2013 15:13, Oleg Kalnichevski ol...@apache.org wrote: On Tue, 2013-01-15 at 14:30 +, ol...@apache.org wrote: Author: olegk Date: Tue Jan 15 14:10:42 2013 New Revision: 1433427 URL: http://svn.apache.org/viewvc?rev=1433427view=rev Log: Updated project web site for HttpClient 4.2.3 release [This commit notification would consist of 6158 parts, which exceeds the limit of 50 ones, so it was shortened to the summary.] I don't know. At the moment the new shiny SvnPubSub thing feels, well, awkward. It took me close to 4 hours to commit updates to the project web site. The largest chunk of module specific files appear to be Clover coverage reports. It would help enormously if we did not have to commit those to the SVN repository. Besides, Clover Maven plugin is a major pain in the rectum by itself due to compatibility issues with Maven 3. I would like to propose Clover reports be removed from the release process. Clover reports are to be generated independently of the release process using a separate Maven profile (or maybe even using Gradle). OK by me. A separate profile would be easy to use and should be fairly simple to implement. They could be published to people.apache.org every once in a while, if desired. That may not be possible long-term, as infra want to limit the need for shell access to minotaur. Oleg Hallelujah! Clover 3.1.x license is now available to the ASF committers. Upgrading to clover plugin 3.1.10 fixed all Clover issues. We can now mandate the use of Maven 3.0.x for building trunks of all HC modules. Oleg - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
Re: Clover 3.1.x license is now available!!! was Re: svnpubsub misery (dropping Maven Clover reports)
Where is our Clover license? G On Tue, Jan 15, 2013 at 4:52 PM, Oleg Kalnichevski ol...@apache.org wrote: On Tue, 2013-01-15 at 16:26 +, sebb wrote: On 15 January 2013 15:13, Oleg Kalnichevski ol...@apache.org wrote: On Tue, 2013-01-15 at 14:30 +, ol...@apache.org wrote: Author: olegk Date: Tue Jan 15 14:10:42 2013 New Revision: 1433427 URL: http://svn.apache.org/viewvc?rev=1433427view=rev Log: Updated project web site for HttpClient 4.2.3 release [This commit notification would consist of 6158 parts, which exceeds the limit of 50 ones, so it was shortened to the summary.] I don't know. At the moment the new shiny SvnPubSub thing feels, well, awkward. It took me close to 4 hours to commit updates to the project web site. The largest chunk of module specific files appear to be Clover coverage reports. It would help enormously if we did not have to commit those to the SVN repository. Besides, Clover Maven plugin is a major pain in the rectum by itself due to compatibility issues with Maven 3. I would like to propose Clover reports be removed from the release process. Clover reports are to be generated independently of the release process using a separate Maven profile (or maybe even using Gradle). OK by me. A separate profile would be easy to use and should be fairly simple to implement. They could be published to people.apache.org every once in a while, if desired. That may not be possible long-term, as infra want to limit the need for shell access to minotaur. Oleg Hallelujah! Clover 3.1.x license is now available to the ASF committers. Upgrading to clover plugin 3.1.10 fixed all Clover issues. We can now mandate the use of Maven 3.0.x for building trunks of all HC modules. Oleg - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org JUnit in Action, 2nd Ed: http://goog_1249600977http://bit.ly/ECvg0 Spring Batch in Action: http://s.apache.org/HOqhttp://bit.ly/bqpbCK Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
Re: Clover 3.1.x license is now available!!! was Re: svnpubsub misery (dropping Maven Clover reports)
On Tue, 2013-01-15 at 16:54 -0500, Gary Gregory wrote: Where is our Clover license? G The same place https://svn.apache.org/repos/private/committers/donated-licenses/clover Oleg On Tue, Jan 15, 2013 at 4:52 PM, Oleg Kalnichevski ol...@apache.org wrote: On Tue, 2013-01-15 at 16:26 +, sebb wrote: On 15 January 2013 15:13, Oleg Kalnichevski ol...@apache.org wrote: On Tue, 2013-01-15 at 14:30 +, ol...@apache.org wrote: Author: olegk Date: Tue Jan 15 14:10:42 2013 New Revision: 1433427 URL: http://svn.apache.org/viewvc?rev=1433427view=rev Log: Updated project web site for HttpClient 4.2.3 release [This commit notification would consist of 6158 parts, which exceeds the limit of 50 ones, so it was shortened to the summary.] I don't know. At the moment the new shiny SvnPubSub thing feels, well, awkward. It took me close to 4 hours to commit updates to the project web site. The largest chunk of module specific files appear to be Clover coverage reports. It would help enormously if we did not have to commit those to the SVN repository. Besides, Clover Maven plugin is a major pain in the rectum by itself due to compatibility issues with Maven 3. I would like to propose Clover reports be removed from the release process. Clover reports are to be generated independently of the release process using a separate Maven profile (or maybe even using Gradle). OK by me. A separate profile would be easy to use and should be fairly simple to implement. They could be published to people.apache.org every once in a while, if desired. That may not be possible long-term, as infra want to limit the need for shell access to minotaur. Oleg Hallelujah! Clover 3.1.x license is now available to the ASF committers. Upgrading to clover plugin 3.1.10 fixed all Clover issues. We can now mandate the use of Maven 3.0.x for building trunks of all HC modules. Oleg - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
