-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Unify version properties names in build-parent #280
Comments
While I don't have a strong opinion, the general convention is: I believe the reason is purely a developer experience thingy. When you import the dependency, you know the artifactId, so the autocompletion narrows the number of choices. If you just start typing |
important: this impact the release scripts. |
I think this has been fixed now? |
No, we still have If we decide to go with the Personally, I don't care, let's just decide and be consistent. Just changing the Jandex one is obviously the easy path. |
Well, I personally prefer the Also note that |
FWIW, WildFly, is more |
This seems to be resolved now |
This follows up issue #275. I think we should use something like
version.foo-name
, e.g.version.jandex
orversion.opentracing-jaxrs
.The text was updated successfully, but these errors were encountered: