+1
We should try to be consistent in which tools we use across the sub projects
Thanks,
Chris
On 16/06/2014 18:35, Vincent Hennebert wrote:
On 16/06/14 17:50, Simon Steiner wrote:
Hi,
Its there in fop, its not in pdfplugin which is where I added it.
Ah, sorry, I didn’t realise the modification was made in the PDF Images
plug-in. I guess it’s ok then, although it would be better to use the
same tool in every sub-project.
Vincent
Thanks
-----Original Message-----
From: Vincent Hennebert [mailto:[email protected]]
Sent: 16 June 2014 16:32
To: [email protected]
Subject: Re: svn commit: r1600897 -
/xmlgraphics/fop-pdf-images/branches/Temp_FontMerging/build.xml
Hi Simon,
On 16/06/14 17:13, Simon Steiner wrote:
Hi,
Seems we have JaCoCo on trunk, I forgot about that. I added emma to
pdfplugin since i have used that tool in the past. I can revert this
change if emma is not allowed.
It’s not so much that Emma is not allowed, it’s that JaCoCo is
already there that provides the same functionality, plus it’s meant
to be the successor of Emma. So we might as well use it.
Thanks,
Vincent
Thanks
-----Original Message-----
From: Vincent Hennebert [mailto:[email protected]]
Sent: 06 June 2014 18:50
To: [email protected]
Subject: Re: svn commit: r1600897 -
/xmlgraphics/fop-pdf-images/branches/Temp_FontMerging/build.xml
On 06/06/14 16:21, ssteiner wrote:
Author: ssteiner
Date: Fri Jun 6 14:21:57 2014
New Revision: 1600897
URL: http://svn.apache.org/r1600897
Log:
Add emma
Why, when we already have JaCoCo?
https://issues.apache.org/jira/browse/FOP-1991
Vincent
