Where from "has private access in " is logged? I'd like to suppress it

Jonathan Gibbons jonathan.gibbons at oracle.com
Thu Feb 24 14:45:53 PST 2011


I think you need to investigate the annotation processors contained in 
dp4j-1.0-jar-with-dependencies.jar  for the source of your problem.  
This (still) does not seem to be a javac issue.

-- Jon

On 02/24/2011 02:27 PM, Gabriele Kahlout wrote:
> On Thu, Feb 24, 2011 at 11:11 PM, Jonathan Gibbons
> <jonathan.gibbons at oracle.com>  wrote:
>> Gabriele,
>> You are not providing sufficient information to determine whether or not
>> there is a javac issue.  Can you provide a simple reproducible test case?
> It is (and was) in link [2]!  Or are you after a sample java project
> that does dp4j on a single sample? I've a stripped down dp4j that
> helped me identify the problem (to this level); I could strip it
> further.
> While I access trees.getScope(..) the JCTree passed contains invalid
> access. At that point it doesn't seem to print anything yet (tracing
> the source calls indeed don't seem to log anything). I'll then remove
> the inaccessible access and replace it with reflection api accesible
> access.  But when the code is compiled with javac the prints will
> appear. Should they? Where do they read from? Not the CompilationUnit,
> since once the annotation processor finished it's all accessible
> compilable code.
>> If not, we cannot help you.
>> -- Jon
>> On 02/24/2011 01:42 PM, Gabriele Kahlout wrote:
>>> The bad news is that it seems javac uses it, not I (that indeed makes
>>> sense). Please object if I'm misunderstanding.
>>> NetBeans team: is there a quick option to suppress those from
>>> NetBeans? The way to go is the scope as I described earlier, but if
>>> supressing is readily available from NB it would be a good quick
>>> option.
>>> On Thu, Feb 24, 2011 at 8:35 PM, Gabriele Kahlout
>>> <gabriele at mysimpatico.com>    wrote:
>>>> The good news is that it's in tools.jar which I could modify and build
>>>> against.

More information about the compiler-dev mailing list