-
Notifications
You must be signed in to change notification settings - Fork 20
Proper handling of project versioning for new releases #59
Copy link
Copy link
Open
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Milestone
Description
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Type
Projects
Status
Done
Status
🔖 Ready
There is no updating of versions in the maven project pom files for new releases at the moment, see sample here :
https://github.com/konveyor/java-analyzer-bundle/blob/v0.3.0-alpha.2/pom.xml#L8
Also the versions of these artifacts do not seem aligned with konveyor versioning , at the moment they are 1.0.0
The SNAPSHOT versioning in maven is a moving pointer meant for development purposes , proper lifecycle procedures to version the artifacts correctly should be implemented at least for official final releases