-
Notifications
You must be signed in to change notification settings - Fork 167
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
[MCOMPILER-538] Do not add target/generated-sources/annotations to the source roots #191
base: maven-compiler-plugin-3.x
Are you sure you want to change the base?
[MCOMPILER-538] Do not add target/generated-sources/annotations to the source roots #191
Conversation
1fb1448
to
a47f454
Compare
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.
This needs a test.
I need to think about the bug but I'm not 100% sure the issue is correct. This might be working as it should.
I have been checking the javac options, and testing with this change, it does seem that we don't need to specify the generated-sources/annotations in the -sourcepath argument, it should be more than enough to specify it on the -s option. |
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 can not confirm that fix resolve issue, IT will be appreciated
All my projects that test upgrades to 3.12.0 fail because of this line, looking forward to when it's removed! |
@Nthalk We need more details. There is a version 3.12.1 under vote, will be available in a few day. |
I'm using renovate for auto dependency upgrades on multiple projects, the simplest doesn't use any annotation processing and yields this error on
The configuration I have is pretty simple, no funny business:
Here is the output of
|
@Nthalk version 3.12.1 is going to be released in a couple of days fixing that issue. |
a47f454
to
5910df7
Compare
I have rebased the PR and added a test case. I am not really happy with the hardcoded paths in |
5910df7
to
9b86939
Compare
Fix for MCOMPILER-538.
The
generatedSourcesPath
will still be added to the maven project paths.Following this checklist to help us incorporate your
contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
[MCOMPILER-XXX] - Fixes bug in ApproximateQuantiles
,where you replace
MCOMPILER-XXX
with the appropriate JIRA issue. Best practiceis to use the JIRA issue title in the pull request title and in the first line of the
commit message.
mvn clean verify
to make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
mvn -Prun-its clean verify
).If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.