Closed jeremylong closed 7 years ago
We recently added rapture as a dependency to abstract the json implementations and it seems to depend on Java 8. Maybe you can use version 1.0.13 while you cannot migrate to Java 8. Let me know if it works.
Thanks, I changed my script to be:
before_install:
- wget -O ~/codacy-coverage-reporter-assembly.jar https://oss.sonatype.org/service/local/repositories/releases/content/com/codacy/codacy-coverage-reporter/1.0.13/codacy-coverage-reporter-1.0.13-assembly.jar
after_success:
- java -cp ~/codacy-coverage-reporter-assembly.jar com.codacy.CodacyCoverageReporter -l Java -r build-reporting/target/coverage-reports/jacoco.xml
This works, as long as any new required features don't show up in newer version of the Codacy Coverage Reporter.
As a build plugin author myself I've been very careful to ensure tools work with older versions of Java as people are slow to upgrade. I'm not sure about the sbt space, but in Maven I've used animal-sniffer-maven-plugin
to ensure my dependencies don't exceed the minimum Java version I want to support.
Thanks!
To correct my statement above - I use animal sniffer to make sure I don't accidentally call a newer API. I use travis-ci running with Java 7 to ensure I don't upgrade a dependency that exceeds my minimum Java level for a plugin.
Regardless, this issue can be closed.
We need to check if there is something similar to Scala and improve the release process. Thanks for the tip.
Build on travis-ci for OWASP dependency-check fails to post results to Codacy due to the use Java 8 APIs within the codacy-coverage-reporter (or one of its dependencies). The README indicates that Java 7 can be used.
java.time.format.DateTimeFormat was added in Java 1.8.
JDK
OpenJDK 1.7.0_80
Expected Behavior
Actual Behavior
The codacy-coverage-reporter fails with the following exception:
Reproducible Test Case
The failing project can be found on github here.
To view the stack trace described above you must go to the travis build that looks like a success found here, scroll to the bottom and then click on the
after_success
button.