Releases: ayeseeem/icm-bits-java
v0.2.4
Another failed attempt to get mvn release:deploy to work properly when deploying to GitHub Packages.
This time, tried mvn -Dmaven.wagon.http.pool=false release:deploy but downgraded to Maven version 3.2.2, after problems deploying the sources .jar, as shown by v0.2.3. This was suggested by
https://stackoverflow.com/questions/4251488/maven-release-plugin-fails-source-artifacts-getting-deployed-twice/37702241#37702241
This took me back to an earlier failure mode:
javax.net.ssl.SSLException: hostname in certificate didn't match: <maven.pkg.github.com> != <*.registry.github.jpy.wang> OR <*.registry.github.jpy.wang> OR <registry.github.com>
v0.2.3
Package org.ayeseeem.icm-bits-java v0.2.3.
Another failed attempt to get mvn release:deploy to work properly when deploying to GitHub Packages.
This time, tried mvn -Dmaven.wagon.http.pool=false release:deploy.
JAR and POM uploaded again. .jar.md5 and .pom.md5 failed to upload.
Failed to upload checksum org/ayeseeem/icm-bits-java/maven-metadata.xml.sha1
Failed to deploy artifacts: Could not transfer artifact org.ayeseeem:icm-bits-java:jar:sources:0.2.3 from/to github (https://maven.pkg.github.com/ayeseeem/icm-bits-java): Transfer failed for https://maven.pkg.github.com/ayeseeem/icm-bits-java/org/ayeseeem/icm-bits-java/0.2.3/icm-bits-java-0.2.3-sources.jar 400 Bad Request
v0.2.2
Package org.ayeseeem.icm-bits-java v0.2.2.
Another attempt at deploying to GitHub Packages as part of mvn release:perform.
Another failure - POM and JAR deployed, but .md5 uploads failed, failing the release:perform step, leaving in an inconsistent state.
v0.2.1
Package org.ayeseeem.icm-bits-java v0.2.1.
Should be the same as v0.2, just trying to get deployment to GitHub Packages working.
.pom and .jar deployed OK, but .pom.md5 and .jar.md5 failed to deploy with 400 Bad Request
v0.2
Added container helpers: static factory methods listOf(), setOf(), keySortedMap(), and insertionOrderedMap().