gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Kalnichevski <ol...@apache.org>
Subject Re: svn commit: r759456 - /gump/metadata/project/httpcomponents.xml
Date Mon, 30 Mar 2009 10:11:33 GMT
On Mon, 2009-03-30 at 06:24 +0200, Stefan Bodewig wrote:
> On 2009-03-28, Oleg Kalnichevski <olegk@apache.org> wrote:
> 
> > On Sat, 2009-03-28 at 16:13 +0100, Stefan Bodewig wrote:
> >> Hi Oleg
> 
> >> On 2009-03-28, <olegk@apache.org> wrote:
> 
> >>> URL: http://svn.apache.org/viewvc?rev=759456&view=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-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Mime
View raw message