-
Notifications
You must be signed in to change notification settings - Fork 194
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
fix build warnings and revert compiler workaround #3813
Conversation
Seems one test is now failing |
[INFO] Annotation processing is enabled because one or more processors were found on the class path. A future release of javac may disable annotation processing unless at least one processor is specified by name (-processor), or a search path is specified (--processor-path, --processor-module-path), or annotation processing is enabled explicitly (-proc:only, -proc:full). Use -Xlint:-options to suppress this message. Use -proc:none to disable annotation processing.
Unfortunately those values are not interchangeable anymore, when using the release attribute.
The fix has been released in 3.12.1, we depend on 3.13.0 now.
I left away the "source/target to release" commit. But I must admit that was just guessing. If it still fails, I will have to run integration tests locally (which I try to avoid). |
@Bananeweizen do you want to squash or merge the individual commits? Also for tycho4? |
There is nothing that would cause functional changes in Tycho itself, therefore this doesn't need to be ported. I tend to not squash independent changes, even though it means that all except the last have not been tested in isolation. If something comes up later, reverting one of the changes seems easier to me than reverse-engineering the original "splitting" of the squashed commit. |
All commits except the last fix certain warnings that are shown during the build. See the commit messages for details.
The last commit is unrelated in the sense that it reverts a maven compiler workaround. However, sending it as separate PR would lead to a conflict, therefore it has been added here.