According to my plans, Surefire 2.8 is 1-2 weeks from now, keeping a
nice 6 week schedule ;)

There are a few bugs in the "reporting" part of surefire Jira that I
somehow don't want to start touching as long as we're on 
a fairly old version of doxia.

So it's just the "business as usual" stuff - inch by inch zapping away
at accumulated bugs ;) 

And if you do manage take a look at it, I will be following up 
trying to fix some issues (and in that process testing).

(And yes, I did try digging the mailing list archives to try to
solve this myself before giving up ;)

Kristian





ma., 28.02.2011 kl. 13.46 +0100, skrev Lukas Theussl:
> I'll have look but it might not be trivial... is there any special 
> reason why you want to upgrade now?
> 
> -Lukas
> 
> 
> Kristian Rosenvold wrote:
> > There seem to be a few compatibility breaks and maybe some incorrect
> > usage within the surefire-report-plugin that is making it hard to
> > upgrade.
> >
> > I was wondering if anyone could help me with this upgrade ?
> >
> > http://jira.codehaus.org/browse/SUREFIRE-566
> >
> > If I just do:
> > svn co https://svn.apache.org/repos/asf/maven/surefire/trunk surefire
> > cd surefire
> > mvn -DskipTests install # lazy me
> > cd surefire-integration-tests/src/test/resources/result-counting
> > mvn -Dsurefire.version=2.7.3-SNAPSHOT surefire-report:report
> > firefox target/site/surefire-report.html
> >
> > Even before I do the update there is something fishy here, since inside
> > the header block I see this:
> > <meta content="text/html; charset=${outputEncoding}"
> > http-equiv="Content-Type">
> >
> > If I apply the patch I have attached at 566 it basically all just stops
> > working ;) (There is no javascript emitted at all and just looking at
> > the HTML source reveals trouble ;) (For instance "detail" link does not
> > work)
> >
> > Anyone ?
> >
> > Kristian
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to