Publishing preparation #3
Conversation
brokkoli71
commented
Jun 24, 2024
brokkoli71
commented
- created deploy.yml for deployment pipeline
- signing with GPG
- prepare pom.xml for publishing
* add zarrita python script * add testReadFromZarrita * renamed zarrita_write * add testWriteToZarrita * parameterized codecs in testReadFromZarrita * fixed camelcase in zarr.json * add venv for executing zarrita in linux * adapt test-setup for linux * adapt test-setup for linux * fix testReadFromZarrita for gzip * parameterize codecs in testReadFromZarrita * remove unused imports * add testCodecsWriteRead * reformat * remove unnecessary argument * add testCodecTranspose * start remove constants "C" adn "F" from Transpose Codec's order * add CoreArrayMetadata to codec object instead of passing as argument in encode and decode remove transpose order "F" and "C" * remove wrong dependency * set fail-fast: false * specify testSourceDirectory * added property index_location to ShardingIndexedCodec * add indexLocation in ShardingCodec. * change junit version for TestUtils * remove creation of dir testdata * update dependencies for JUnit 5 * install zarrita in CI * correct python version, maven no-transfer-progress * add venv for executing zarrita to CI * add /venv_zarrita to .gitignore * remove deprecated zarrita venv * test CI * fix tests for windows * update python path for windows in ci.yml * add Development Start-Guide to Run Tests Locally * correct Development Start-Guide to python3.11 * add support of shardingCodec indexLocation=start * code cleanup * add testZstdLibrary * fix Zstd compression and decompression * cleanup code * cleanup code * remove unused method * include crc32c codec into tests * incorporate feedback for java version and merge tests * add more variation to codec-configuration in tests with zarrita * fix BloscCodec with shuffle = "shuffle"
|
@sbesson What do you think about the name of the package for publishing? I remember you didn't like dev.zarr.zarrjava. We probably can't use just dev.zarr anymore. |
I'd defer to @joshmoore and owners of the https://zarr.dev/ domain but my preference would have gone for |
|
Ack. I did not see this! 🤦🏽 x2 today. I'm reviewing the diff between this and #4 now. Apologies, @brokkoli71. |
|
@brokkoli71: apologies. Didn't realize there were no tests run on zarr-java2. My merge duplicated a tag: Could you remove or shall I open another PR? |
No worries, @joshmoore. Let me know if there's anything I can assist with. |
|
https://repo1.maven.org/maven2/dev/zarr/zarr-java/0.0.2/ thanks all. We'll start consuming this |
