Switch from Travis-CI to GitHub Actions#66
Conversation
- maven-changes-plugin -> 2.12.1 - maven-jxr-plugin -> 3.2.0 - maven-compiler-plugin -> 3.10.1 - maven-source-plugin -> 3.2.1 - maven-jar-plugin -> 3.2.2 - maven-javadoc-plugin -> 2.10.4 - maven-surefire-plugin -> 2.19.1 - maven-project-info-reports -> 3.3.0 - maven-site-plugin -> 4.0.0-M1 - maven-bundle-plugin -> 5.1.6 - junit -> 4.13.2
|
I think this is ready now... |
|
Java 16 is an intentionally ignored (for now) failure (see #67). |
|
@ralphlange should we just skip jdk16 for the time being ( we keep the issue ticket open to document all that you have done ) |
|
Your call. I configured it to not fail the build and kept it so we always have it on our radar that there is an issue to be fixed. |
|
Could you comment out the jdk16 inclusion - this was the comments remain in place as a reminder but the CI for the main project appears green. |
|
I don't understand. Again: I added the configuration to have that job not fail the build. I.e., the CI for the main project appears green even though the Java 16 build is failing. (See https://github.com/ralphlange/jca/actions/runs/2703430640 for an example.) |
|
the thing is all PR's will have the "some failing" bit... which is what I was referring to. |
|
Thanks! |
2 participants
ssia