-
Notifications
You must be signed in to change notification settings - Fork 189
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
Maven ReadOnlyPluginParametersValidator triggered by tycho-p2-publisher #2644
Comments
See also this discussion: Sadly Maven has recently added a lot of validations that emit many warnings for code that previously worked without any issue and without any clear migration guide... |
So, how to proceed? Can something be done on the Tycho side? Should we report this to Maven? Or what? |
laeubi
added a commit
to laeubi/tycho
that referenced
this issue
Dec 3, 2023
laeubi
added a commit
that referenced
this issue
Dec 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tycho-p2-publisher injects the build qualifier into the Maven model. However, on recent Maven versions that triggers one of the core validators: https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/plugin/internal/ReadOnlyPluginParametersValidator.java
Therefore the goals of the p2-publisher then emit one warning each for having a value set for a read-only property. I'm not sure if there is a good way to work around the validation, but of course I would like to have my build show no warnings.
The text was updated successfully, but these errors were encountered: