René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Support individual component version release","articleBody":"This repository is structured as a multi-module Maven project except that each \"module\" is treated as distinct and inherits from `pom-scijava` instead of a single reactor `pom.xml` in the project.\n\nFor the initial release of SciJava Ops we were able to get away with keeping all intra-repo dependencies at `project.version` because each project was at the same `1.0.0` version. However, this left us with technical debt for releasing future individual components. We *do not* want to bump *all* component versions each time a single component needs release, as this creates a large amount of vacuous releases that are likely meaningless and violate (or at least mislead) SemVer.\n\nFirst requirement, as standalone projects:\n- [ ] All individual projects should have entries in the `dependencyManagement` section of the [pom-scijava](https://github.com/scijava/pom-scijava/tree/master) bill of materials, with appropriately named `component.version` properties defined.\n\nProblem 1:\nUnfortunately, although these projects should be managed in `pom-scijava`, these are all release versions. Within the reactor we still want `SNAPSHOT` versions for these dependencies so that changes in one are immediately reflected in another, thus we can't actually use the `component.version` properties inherited from `pom-scijava`.\n**Discussion point:** is this a technical requirement or one of convenience? If we keep everything release-coupled, the development process would be no different than if the projects were in separate repositories (e.g. manually pinning to `SNAPSHOT`s or \"fake\" versions for local testing) and we wouldn't have to worry about the enforcer, right?\n\nProblem 2:\nThe [maven-release plugin](https://maven.apache.org/maven-release/maven-release-plugin/), and our [release-version.sh](https://github.com/scijava/scijava-scripts/blob/0e97dd09375b32892b61a81ca3b9bff56fb801f7/release-version.sh) script, don't support releasing individual components out of a multi-module reactor. Therefore we currently have no way to actually perform component releases reliably.\n\nSecond requirement:\n- [ ] Create a new release script, for a single component in a multi-module reactor:\n  * Manually performs any required `maven-release` steps\n  * Creates a `component-name-component-version` tag with the release commit\n  * Updates version properties in other components?'\n  * ... what else?","author":{"url":"https://github.com/hinerm","@type":"Person","name":"hinerm"},"datePublished":"2025-01-16T20:50:32.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/281/scijava/issues/281"}