Re: svn commit: r759456 - /gump/metadata/project/httpcomponents.xml
On 2009-03-30, Oleg Kalnichevski ol...@apache.org wrote: On Mon, 2009-03-30 at 06:24 +0200, Stefan Bodewig wrote: You really only need to add a junitreport element that points to the surefire target directory and all test reports are published. Sorry it isn't documented in an obvious way. Did that (see commit messages), but surefire-reports link always pointed at an empty folder. I'll take a look at that, hmm, looks as if there was just a directory level missing. The build log says , | Surefire report directory: /srv/gump/public/workspace/httpcomponents/httpcore/httpcore/target/surefire-reports ` which is one httpcore more than the Gump descriptor contains. I'll fix that. home doesn't apply to junitreport, maybe it should. I did try hard before giving up. In no way did I want to question that. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r759456 - /gump/metadata/project/httpcomponents.xml
On Mon, 2009-03-30 at 06:24 +0200, Stefan Bodewig wrote: On 2009-03-28, Oleg Kalnichevski ol...@apache.org wrote: On Sat, 2009-03-28 at 16:13 +0100, Stefan Bodewig wrote: Hi Oleg On 2009-03-28, ol...@apache.org wrote: URL: http://svn.apache.org/viewvc?rev=759456view=rev Log: Giving up on Gump Why is that, what is causing trouble to you? I don't recall any specific incidents. There several reasons that led me to this decision. (1) Gump has been Maven2 unfriendly for quite some time. I'd say it is the other way around, but I'm certainly biased. 8-) Just a small example. Every change of an artifact version in a project's POM causes Gump build failure, requiring a manual update of the Gump metadata. While not such a big deal, this can be quite a nuisance during the release process when so many things need to be taken care of. Yes, this is a pain. We'd immediately fix that in Gump if only we could. We've tried to set the artifact name related properties on the mvn command line (as we've been told to do), but it simply doesn't work. (2) Just recently HttpCompopnents Core build has been failing for several days in a row. Despite all my attempts to figure out _what_ exactly was causing the failure, I just could not. All tests seemed to pass. Most likely a change upstream. You see, guessing does not really help. I simply could not extract any helpful information from the Gump report which could help me identify the cause of the failure. At the same time I could not find a way to get hold of the surefire reports to double-check. It was all just a bit too much for me and I gave up. You really only need to add a junitreport element that points to the surefire target directory and all test reports are published. Sorry it isn't documented in an obvious way. Did that (see commit messages), but surefire-reports link always pointed at an empty folder. I did try hard before giving up. Oleg - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r759456 - /gump/metadata/project/httpcomponents.xml
On Sat, 2009-03-28 at 16:13 +0100, Stefan Bodewig wrote: Hi Oleg On 2009-03-28, ol...@apache.org wrote: Author: olegk Date: Sat Mar 28 11:40:36 2009 New Revision: 759456 URL: http://svn.apache.org/viewvc?rev=759456view=rev Log: Giving up on Gump Why is that, what is causing trouble to you? I don't recall any specific incidents. Hi Stefan There several reasons that led me to this decision. (1) Gump has been Maven2 unfriendly for quite some time. Just a small example. Every change of an artifact version in a project's POM causes Gump build failure, requiring a manual update of the Gump metadata. While not such a big deal, this can be quite a nuisance during the release process when so many things need to be taken care of. (2) Just recently HttpCompopnents Core build has been failing for several days in a row. Despite all my attempts to figure out _what_ exactly was causing the failure, I just could not. All tests seemed to pass. At the same time I could not find a way to get hold of the surefire reports to double-check. It was all just a bit too much for me and I gave up. While I understand the unique value of Gump, Continuum is simply more practical for multi-module Maven projects. Oleg Anyway, I have revertedy your changes since other projects might depend on httpcomponents, but I have removed the nag emails so you don't need to bother if it disturbs you. Many thanks for supporting Gump in the past Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r759456 - /gump/metadata/project/httpcomponents.xml
On 2009-03-28, Oleg Kalnichevski ol...@apache.org wrote: On Sat, 2009-03-28 at 16:13 +0100, Stefan Bodewig wrote: Hi Oleg On 2009-03-28, ol...@apache.org wrote: URL: http://svn.apache.org/viewvc?rev=759456view=rev Log: Giving up on Gump Why is that, what is causing trouble to you? I don't recall any specific incidents. There several reasons that led me to this decision. (1) Gump has been Maven2 unfriendly for quite some time. I'd say it is the other way around, but I'm certainly biased. 8-) Just a small example. Every change of an artifact version in a project's POM causes Gump build failure, requiring a manual update of the Gump metadata. While not such a big deal, this can be quite a nuisance during the release process when so many things need to be taken care of. Yes, this is a pain. We'd immediately fix that in Gump if only we could. We've tried to set the artifact name related properties on the mvn command line (as we've been told to do), but it simply doesn't work. (2) Just recently HttpCompopnents Core build has been failing for several days in a row. Despite all my attempts to figure out _what_ exactly was causing the failure, I just could not. All tests seemed to pass. Most likely a change upstream. At the same time I could not find a way to get hold of the surefire reports to double-check. It was all just a bit too much for me and I gave up. You really only need to add a junitreport element that points to the surefire target directory and all test reports are published. Sorry it isn't documented in an obvious way. While I understand the unique value of Gump, Continuum is simply more practical for multi-module Maven projects. Gump and Continuum fill totally different needs. IMHO it is no either or but a use both. Use Continuum for your nightly builds and use Gump to detect the impact of your changes to your dependees or changes in your dependencies to you. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r759456 - /gump/metadata/project/httpcomponents.xml
Hi Oleg On 2009-03-28, ol...@apache.org wrote: Author: olegk Date: Sat Mar 28 11:40:36 2009 New Revision: 759456 URL: http://svn.apache.org/viewvc?rev=759456view=rev Log: Giving up on Gump Why is that, what is causing trouble to you? I don't recall any specific incidents. Anyway, I have revertedy your changes since other projects might depend on httpcomponents, but I have removed the nag emails so you don't need to bother if it disturbs you. Many thanks for supporting Gump in the past Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
