Upgrade Jetty to version 10.x.

[kdombeck]

Other libraries were upgraded to their latest versions as well.

Implementation for #32

[kdombeck]

I incremented the minor version since this uses a newer version of Jetty.

[kdombeck]

This "could" be left at 8 but I updated it to 11 since Jetty 10+ requires Java 11+.

[kdombeck]

I did not upgrade to Jetty 11+ since that requires JakartaEE instead of javax. Guice does not support that yet.

[kdombeck]

Guice did not need to be upgraded as all tests passed without upgrading it. So it could be downgraded if older version would be preferred.

[kdombeck]

Needed to upgrade this plugin otherwise when building on new JVMs it generated the following error.

Execution attach-javadocs of goal org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar: java.lang.ExceptionInInitializerError: null

Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end 3, length 2
    at java.lang.String.checkBoundsBeginEnd (String.java:3319)
    at java.lang.String.substring (String.java:1874)
    at org.apache.commons.lang.SystemUtils.getJavaVersionAsFloat (SystemUtils.java:1133)
    at org.apache.commons.lang.SystemUtils.<clinit> (SystemUtils.java:818)

[ofir-popowski]

Thank you for your submission @kdombeck :)

Since your PR changes to use JDK11, I have changed the Github action to use JDK11. Build should run now if you update your branch from master

[ofir-popowski]

I think this should be okay :)

[ofir-popowski]

@kdombeck okay so, it seems like the current setup to publish this to the maven repository isn't working. I'm going to have to spend some time setting it up correctly (probably with a github action) and let you know once it's published

[kdombeck]

@kdombeck okay so, it seems like the current setup to publish this to the maven repository isn't working. I'm going to have to spend some time setting it up correctly (probably with a github action) and let you know once it's published

Thank you!!

[ofir-popowski]

@kdombeck I would like to extend an apology. I haven't had time to do what I said in my previous comment yet. I'll try to prioritize this as much as I can

[kdombeck]

@kdombeck I would like to extend an apology. I haven't had time to do what I said in my previous comment yet. I'll try to prioritize this as much as I can

No need to apologize. Thank you for looking into this.

[kdombeck]

@ofir-popowski is there anything that I can help with to get this published to Maven?

[ofir-popowski]

@kdombeck heya, i think i finally managed to get this sorted
try changing the dependency to io.logz:guice-jersey:1.1.05 and see if it works out

[kdombeck]

@kdombeck heya, i think i finally managed to get this sorted try changing the dependency to io.logz:guice-jersey:1.1.05 and see if it works out

Thank you!!

I did a quick test and it appears to be working. I did have a couple of questions.

• Why is the patch version 05? Looking at Semantic Versioning it states that versions must not have leading zeros.
• Shouldn't the version in the pom.xml be updated to match the released version?

[ofir-popowski]

Oh thank you for pointing these out :)
It was my first time adding a Github Action and doing a release and all that so I'm still working out some kinks :p

[asafm]

@ofir-popowski Take a look at the jmx2graphite repo: https://github.com/logzio/jmx2graphite
It has GitHub Actions such as when you create a release, it updates the pom.xml version matching the release name