Rules about versioning GlassFish and GlassFish project components (HK2, Grizzly, etc.) #25539
OndroMih
started this conversation in
GlassFish Development
Replies: 1 comment
-
I believe it was resolved long ago, there are also general standards about it. Upgrading Dependencies
Releasing
Since Then
TODO
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, fellow GlassFish committers,
I'd like to bring this point after coming across this issue raised for HK2: eclipse-ee4j/glassfish-hk2#888
The issue is that versioning of releases and upgrading dependencies is sometimes taken lightly, without much consideration. Often dependencies suggested by dependabot are routinely merged and new component releases often just increase a patch version where they should increase a minor or major version.
I want to start this discussion to align on some simple rules about merging dependencies, introducing breaking changes, and versioning. Especially for components like HK2 or Grizzly, because I think we already handle this well in the main GlassFish repository.
I suggest the following to consider:
What do others think?
Can we introduce some maven plugin that ensures some of these rules? Does anybody know about such a plugin?
Ondro
Beta Was this translation helpful? Give feedback.
All reactions