Implement maven-release-plugin #14

New Issue

bea · 2023-01-16T02:41:50+01:00

bea commented

2023-01-16 02:41:50 +01:00

We should set the project up so that development changes and builds happen in the dev branch. Those builds should all have x.y.z-SNAPSHOT as a version and be higher than the latest stable build. Those builds should get deployed by Drone to the snapshots repository.

We should also set up stable builds being pushed in the main branch. Those builds should have a x.y.z-type version and get pushed automatically to the releases repository by Drone.

The maven-release plugin can help in maintaining consistency between version numbers and accidentally forgetting a major version number in a dev build or likewise in a stable build. It can handle automatically committing without the -SNAPSHOT parameter, and then automatically increasing the version number to the nest -SNAPSHOT.

We should find a way to nicely integrate this with Drone, Maven, and two branches.

We should set the project up so that development changes and builds happen in the `dev` branch. Those builds should all have `x.y.z-SNAPSHOT` as a version and be higher than the latest stable build. Those builds should get deployed by Drone to the `snapshots` repository. We should also set up stable builds being pushed in the `main` branch. Those builds should have a `x.y.z`-type version and get pushed automatically to the `releases` repository by Drone. The `maven-release` plugin can help in maintaining consistency between version numbers and accidentally forgetting a major version number in a dev build or likewise in a stable build. It can handle automatically committing without the `-SNAPSHOT` parameter, and then automatically increasing the version number to the nest `-SNAPSHOT`. We should find a way to nicely integrate this with Drone, Maven, and two branches.

bea added the

enhancement

label 2023-01-16 02:41:50 +01:00

Sign in to join this conversation.