Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define the semantic versioning strategy #449

Open
starksm64 opened this issue Dec 7, 2021 · 0 comments
Open

Define the semantic versioning strategy #449

starksm64 opened this issue Dec 7, 2021 · 0 comments
Labels
jea-linked Linked in jakarta-ee-azdo project

Comments

@starksm64
Copy link
Contributor

Is your feature request related to a problem? Please describe.
There is a general desire to support a semantic versioning model across specification artifacts, but we don't have effective tooling to do so. OSGi manifests are inconsistently being used to provide some aspect of this under one module system. We need a general approach with guidelines on usage.

Describe the solution you'd like
We need Jakarta supported tooling in place along with usage guidelines.

Describe alternatives you've considered
There are OSGi annotations and plugins that support the feature. However, there was not universal acceptance of whether such external tools should be employed in Jakarta.

Additional context
A discussion on this topic occurred in a platform meeting, and the following dev thread was started to open the conversation:
https://www.eclipse.org/lists/jakartaee-platform-dev/msg02761.html

@starksm64 starksm64 changed the title Definine the semantic versioning strategy Define the semantic versioning strategy Dec 7, 2021
@arjantijms arjantijms added the jea-linked Linked in jakarta-ee-azdo project label Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jea-linked Linked in jakarta-ee-azdo project
Projects
None yet
Development

No branches or pull requests

2 participants