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

Semver support for Java EE #7

Open
reiz opened this issue Jan 6, 2014 · 0 comments
Open

Semver support for Java EE #7

reiz opened this issue Jan 6, 2014 · 0 comments
Assignees

Comments

@reiz
Copy link
Member

reiz commented Jan 6, 2014

Customer Feedback:

I have the dependency javax.enterprise:cdi-api in version 1.1-20130918 which happen to be more recent than version 1.1 while it's reported as outdated. Java EE APIs are actually using few suffixes that vary with the sematic versionning contrat. Based on their example:

1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-alpha.beta < 1.0.0-beta < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < 1.0.0

While with Java EE APIs:

1.1.EDR1 < 1.1-PFD < 1.1-PRD < 1.1 < 1.1-20130918 < 1.1-SP1

EDR: Early Draft Review PRD: Public Review Draft PFD: Public Final Draft SP: Service Pack This is a mix of suffix semantic plus suffix date. There could be a way to support these use cases so that VersionEye could be even better product.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant