Skip to content
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

Add a custom compile argument replaceProcessorPathWithProcessorModule… #213

Merged
merged 1 commit into from
May 6, 2022

Conversation

slachiewicz
Copy link
Member

…Path to force the plugin replace processorPath with processormodulepath

Closes #191 #192

…Path to force the plugin replace processorPath with processormodulepath

Closes #191 #192
@slachiewicz slachiewicz merged commit 8cc8c9f into master May 6, 2022
@slachiewicz slachiewicz deleted the pr192 branch May 6, 2022 12:35
@@ -206,7 +207,14 @@ public CompilerResult performCompile( CompilerConfiguration config )
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MissingSummary: A summary line is required on public/protected Javadocs.

(at-me in a reply with help or ignore)


Was this a good recommendation?
[ 🙁 Not relevant ] - [ 😕 Won't fix ] - [ 😑 Not critical, will fix ] - [ 🙂 Critical, will fix ] - [ 😊 Critical, fixing now ]


static boolean isReplaceProcessorPath( CompilerConfiguration config )
{
for ( Entry<String, String> entry : config.getCustomCompilerArgumentsEntries() )
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about a modern way doing it?

        return config.getCustomCompilerArgumentsEntries().stream()
                .filter(entry -> entry.getKey().equals( OPT_REPLACE_PROCESSOR_PATH ) || entry.getKey().equals( OPT_REPLACE_PROCESSOR_PATH_ ))
                .findFirst().isPresent();

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, code could be revitalized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

apt not work in jdk > 9
3 participants