Investigate Snapshots

[countableSet]

learning how gradle / maven handles snapshots

directory and file naming structure

.
└── dev
    └── poolside
        └── test
            ├── bom
            │   ├── 0.1.1-SNAPSHOT
            │   │   ├── bom-0.1.1-20220701.044037-1.module
            │   │   ├── bom-0.1.1-20220701.044037-1.module.md5
            │   │   ├── bom-0.1.1-20220701.044037-1.module.sha1
            │   │   ├── bom-0.1.1-20220701.044037-1.module.sha256
            │   │   ├── bom-0.1.1-20220701.044037-1.module.sha512
            │   │   ├── bom-0.1.1-20220701.044037-1.pom
            │   │   ├── bom-0.1.1-20220701.044037-1.pom.md5
            │   │   ├── bom-0.1.1-20220701.044037-1.pom.sha1
            │   │   ├── bom-0.1.1-20220701.044037-1.pom.sha256
            │   │   ├── bom-0.1.1-20220701.044037-1.pom.sha512
            │   │   ├── maven-metadata.xml
            │   │   ├── maven-metadata.xml.md5
            │   │   ├── maven-metadata.xml.sha1
            │   │   ├── maven-metadata.xml.sha256
            │   │   └── maven-metadata.xml.sha512
            │   ├── maven-metadata.xml
            │   ├── maven-metadata.xml.md5
            │   ├── maven-metadata.xml.sha1
            │   ├── maven-metadata.xml.sha256
            │   └── maven-metadata.xml.sha512
            └── my-lib-dep
                ├── 0.1.1-SNAPSHOT
                │   ├── maven-metadata.xml
                │   ├── maven-metadata.xml.md5
                │   ├── maven-metadata.xml.sha1
                │   ├── maven-metadata.xml.sha256
                │   ├── maven-metadata.xml.sha512
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.jar
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.jar.md5
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.jar.sha1
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.jar.sha256
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.jar.sha512
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.module
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.module.md5
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.module.sha1
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.module.sha256
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.module.sha512
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.pom
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.pom.md5
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.pom.sha1
                │   ├── my-lib-dep-0.1.1-20220701.044037-1.pom.sha256
                │   └── my-lib-dep-0.1.1-20220701.044037-1.pom.sha512
                ├── maven-metadata.xml
                ├── maven-metadata.xml.md5
                ├── maven-metadata.xml.sha1
                ├── maven-metadata.xml.sha256
                └── maven-metadata.xml.sha512

7 directories, 45 files

After publishing three version in order 0.1.1-SNAPSHOT, 0.1.1, 0.1.2-SNAPSHOT

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>dev.poolside.test</groupId>
  <artifactId>my-lib-dep</artifactId>
  <versioning>
    <latest>0.1.2-SNAPSHOT</latest>
    <release>0.1.1</release>
    <versions>
      <version>0.1.1-SNAPSHOT</version>
      <version>0.1.1</version>
      <version>0.1.2-SNAPSHOT</version>
    </versions>
    <lastUpdated>20220701044441</lastUpdated>
  </versioning>
</metadata>

to reference a specific version of snapshot

implementation("dev.poolside.test:my-lib-dep:0.1.1-20220701.044037-1")

proposed workflow

auto

1. set version 0.1 without patch version
2. derive the correct patch version (by looking in the repo)
3. if branch add -SNAPSHOT to project version
4. if mainline branch, do nothing and use the derived version
5. done and continue

manual

1. set version 0.1.1 with patch version
2. if branch add -SNAPSHOT to project version
3. if mainline branch, check to see if the version already exists in the repo and disable publishing if needed
4. done and continue