Test of detection of invalid codec order and invalid TransposeCodec

[brokkoli71]

This PR is a small addition to #6 based on #6 (review)

• test if invalid codec orders get detected
• refactored the test for invalid transpose codecs
• both checks during runtime were already implemented

[sbesson]

Thanks @brokkoli71 and @normanrz, great to see additional coverage of this validation logic. From our side, it would be useful to have this feature available in a release artifact. Would it make sense to schedule a patch release of zarr-java or do you have other in-progress work?

Re release, am I correct that all that is needed is to bump the version in the pom.xml, push a tag and the GitHub workflow should handle the deployment to Maven Central?

[normanrz]

Re release, am I correct that all that is needed is to bump the version in the pom.xml, push a tag and the GitHub workflow should handle the deployment to Maven Central?

I just created a new release. Yeah, just create a new tag and the Github CI will take care of deployment. You can even create the new tag from the Github UI via the Releases page.

[sbesson]

Looking at https://github.com/zarr-developers/zarr-java/actions/runs/10505611095/job/29103503907, it looks like the workflow tried to create a 0.0.2 version again. I think

zarr-java/pom.xml

Line 9 in e3e2208

<version>0.0.2</version>

needs to be updated prior to tagging (and maybe we switch back to SNAPSHOT after release as per the standard Java development workflow?)

[normanrz]

🤦 Ok. Thanks for fixing this.