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

get WARNING while maven package with JDK-9 released yesterday. #1471

Closed
xiongchen2012 opened this issue Sep 24, 2017 · 6 comments
Closed

get WARNING while maven package with JDK-9 released yesterday. #1471

xiongchen2012 opened this issue Sep 24, 2017 · 6 comments

Comments

@xiongchen2012
Copy link

$maven package

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by lombok.javac.apt.LombokProcessor to field com.sun.tools.javac.processing.JavacProcessingEnvironment.discoveredProcs
WARNING: Please consider reporting this to the maintainers of lombok.javac.apt.LombokProcessor
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

My lombok version is 1.16.16

JavacTransformer become unresolved?

@xiongchen2012
Copy link
Author

1.16.18 get the same warning.

@ottlinger
Copy link

ottlinger commented Sep 26, 2017

@rspilker
Copy link
Collaborator

rspilker commented Oct 5, 2017

The solution is to add some -J--add-opens arguments to the compiler, however, that won't help you for now because of a bug in the compiler-plugin. Please vote for issue MCOMPILER-291 to get this fixed.

One other thing, it did compile on my machine, but possibly I just didn't fail on warnings.

@ottlinger
Copy link

@rspilker thanks for the reference to MCOMPILER-291 - I tried to add the references, but still get errors .... can you reference a project that works on github/travis? Thanks.

@rspilker
Copy link
Collaborator

The fix is described in #985 (comment)

@techomaxx
Copy link

we can change manually our error through the actual code which written in in maven site or its jar file..
copy and write our program and test what is actual problem..
its maven fault or our programming error or any problem in our own system..
@Sorry when its wrong ...
i'm just give you my point of view..

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

No branches or pull requests

4 participants