robinroos

To launch under Java 17 we are using: `jvm.module.opts=--illegal-access=warn --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.io=ALL-UNNAMED --add-opens java.base/java.time=ALL-UNNAMED`

I have a modest preference for a Supplier -based solution, because the separation of hasNext() and next() in the Iterator contract mandates careful synchronization if the caller (Ikasan framework) is...

I think this github issue tracker has removed all of my < and > characters and enclosed "XML-like" tags, where I specified the Java 8 generic type of an object....

I understand this was tricky and could not be included in 1.6.0, but thanks for trying. I will continue to manually set this property on new deploymentsof snapshot container versions.

This is the best workaround I can find, and for the reasons stated in my opinion the workaround is not good enough. ``` org.codehaus.mojo build-helper-maven-plugin 3.0.0 build-helper-regex-is-snapshot-used regex-property jkube.imagePullPolicy ${project.version}...

I have this approach working now. It is still a "workaround" and I look forward to moving away from it to something less brittle and more understandable. Note that build-helper-maven-plugin...

Thanks for that. We chose the alternative approach and I am expediting our adoption of Java 21.