Github user twogee commented on the issue:
https://github.com/apache/ant-ivy/pull/36
Thanks! BTW I had to keep the "test-coverage" target as an alias because
that's what the Jenkins scripts expect. That's another adjustment for later...
---
If your project is set up for it, you can r
Github user asfgit closed the pull request at:
https://github.com/apache/ant-ivy/pull/36
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Github user janmaterne commented on the issue:
https://github.com/apache/ant-ivy/pull/36
Adressed the deletion by myself.
Left the ASM over for another time.
Merge all ...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user janmaterne commented on the issue:
https://github.com/apache/ant-ivy/pull/36
While not having the result of the clean-run, what about deleting the
jacoco.data file just before running ?
With ASM I could spend a little bit to do a check before ... (something
like:
Github user janmaterne commented on the issue:
https://github.com/apache/ant-ivy/pull/36
Stacktrace is:
C:\projekte\apache-ant\ivy-core\build.xml:492: Error while creating report
at org.jacoco.ant.ReportTask.execute(ReportTask.java:501)
Caused by: java.io.IOException
Github user twogee commented on the issue:
https://github.com/apache/ant-ivy/pull/36
There are reports about the "log" file getting corrupt when it accumulates
results from multiple runs. If 'ant clean' helps, then perhaps the "log" file
must be removed in test-internal target before
Github user janmaterne commented on the issue:
https://github.com/apache/ant-ivy/pull/36
First progress: found an old ASM on Ant's own classpath. Ant 1.9.6 loads
that via fetch.xml. Different topic ...
JaCoCo runs fine. Report generation failed without any hint. Try running
w
Github user twogee commented on the issue:
https://github.com/apache/ant-ivy/pull/36
Revised accordingly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, o
Github user nlalevee commented on the issue:
https://github.com/apache/ant-ivy/pull/36
The build-release.xml seems to be largely modified because of some space at
the end of xml tags. Could we avoid that ? It is painful to review and seems
useless.
---
If your project is set up for
Github user jaikiran commented on the issue:
https://github.com/apache/ant-ivy/pull/36
>> I found out that JUnit tests polute run.classpath by placing an empty
jar in /lib, which breaks eg javadoc. Any ideas which test may do that?
I believe this PR https://github.com/apache/a
Github user twogee commented on the issue:
https://github.com/apache/ant-ivy/pull/36
JaCoCo "log" gets an extension ".data";
JaCoCo reports are generated when JUnit fails;
Checkstyle rules sync'ed with Ant.
Anything else?
I found out that JUnit tests polute run.clas
Github user twogee commented on the issue:
https://github.com/apache/ant-ivy/pull/36
By default, jacoco "log" gets extension ".exec"; I'd rather call it
".data". I can amend the PR later tonight.
Could you please check your classpath for multiple instances of asm? jacoco
need
Github user janmaterne commented on the issue:
https://github.com/apache/ant-ivy/pull/36
The JaCoCo 'logfile' seems to be a binary one. So it should not be named
'*.log'. Maybe 'jacoco-log.bin'?
In 'test-report' the should be the last statement, so we get the
report created.
Github user twogee commented on the issue:
https://github.com/apache/ant-ivy/pull/36
P.S. Any suggestions about finding out which rules do not work in
Checkstyle are much appreciated. I had to resort to trial and error.
Also, Ant includes a [different
variant](https://github.
GitHub user twogee opened a pull request:
https://github.com/apache/ant-ivy/pull/36
Replace emma with jacoco
This modernises the reporting of code coverage.
Please try it out.
NB! On macOS, it tickles https://bugs.openjdk.java.net/browse/JDK-8022291
which is harmless
gt; >> ____
> >> From: Gintautas Grigelionis
> >> Sent: Monday, May 29, 2017 9:50 AM
> >> To: Ant Developers List
> >> Subject: Re: Replace emma with jacoco?
> >>
> >> Talk about timing, again :-) -- Clover
eful
> than typical code coverage plugins.
>
> On 29 May 2017 at 08:55, Martin Gainty wrote:
>
> >
> >
> >
> >
> > From: Gintautas Grigelionis
> > Sent: Monday, May 29, 2017 9:50 AM
> > To: Ant Developers Li
May 2017 at 08:55, Martin Gainty wrote:
>
>>
>>
>>
>>
>> From: Gintautas Grigelionis
>> Sent: Monday, May 29, 2017 9:50 AM
>> To: Ant Developers List
>> Subject: Re: Replace emma with jacoco?
>>
>> Talk about timing, again :
AM
> To: Ant Developers List
> Subject: Re: Replace emma with jacoco?
>
> Talk about timing, again :-) -- Clover has been open source since April.
> BTW, the documentation has moved to https://atlassian-docs.bitbucket.io/,
> Atlassian documentation<https://atlassian-docs.
From: Gintautas Grigelionis
Sent: Monday, May 29, 2017 9:50 AM
To: Ant Developers List
Subject: Re: Replace emma with jacoco?
Talk about timing, again :-) -- Clover has been open source since April.
BTW, the documentation has moved to https://atlassian
d other information from
> sourceforge.net and its partners regarding IT services and products. I
> understand that I can ...
>
>
> WDYT of Clover?
>
> Martin
> ______________
>
>
>
>
> From: Gintautas Grigelionis
> Sent: Sunday, May 28, 2017 9:59 AM
> To:
üngliche Nachricht-
> Von: Martin Gainty [mailto:mgai...@hotmail.com]
> Gesendet: Montag, 29. Mai 2017 00:58
> An: Ant Developers List
> Betreff: Re: Replace emma with jacoco?
>
> Hi Gintautas
>
>
> clover code-coverage has been around for 15 years..atlassian just
tautas Grigelionis
Sent: Sunday, May 28, 2017 9:59 AM
To: Ant Developers List
Subject: Replace emma with jacoco?
As you could understand by now, I set a goal of getting all targets in
build.xml to do what they are supposed to do. Which brings us to emma,
which appears no longer being developed. D
As you could understand by now, I set a goal of getting all targets in
build.xml to do what they are supposed to do. Which brings us to emma,
which appears no longer being developed. Do we need a vote about a
replacement?
Gintas
24 matches
Mail list logo
