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
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
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:
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
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,
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
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
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
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
12 matches
Mail list logo
