-
Notifications
You must be signed in to change notification settings - Fork 148
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
Fixes Jakarta Servlet API version #25032
Fixes Jakarta Servlet API version #25032
Conversation
Signed-off-by: Alexander Pinčuk <[email protected]>
@@ -883,12 +883,12 @@ | |||
<artifact> | |||
<groupId>jakarta.servlet</groupId> | |||
<artifactId>jakarta.servlet-api</artifactId> | |||
<version>${servlet-api.version}</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder why this missing property didn't bother the plugin...
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Signed-off-by: Alexander Pinčuk <[email protected]>
I suppose: maven resolver tries to download specified version (#25032 (comment)) but there is no such property to be interpolated so it stays as is. |
Aha, I got it, dependencies are specified correctly (except tests, where it is reported as an error by Eclipse IDE; maybe those tests fail to compile but bash script ignores the result? We should check ...), just the spec plugin is wrong and unfortunately doesn't crash the build even with unresolved properties. Good catch! |
Fixes Jakarta Servlet API version in various POMs.
If we build GlassFish with the empty maven cache:
the local maven repo contains strange artifact: