[ 
https://issues.apache.org/jira/browse/LOG4J2-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081722#comment-14081722
 ] 

Remko Popma commented on LOG4J2-756:
------------------------------------

Yes, copy-paste error. I noticed after pressing Enter... :-( There may be some 
svn magic to fix it but I don't have time to investigate.

> Stray Log4j2Plugins.dat appears during build
> --------------------------------------------
>
>                 Key: LOG4J2-756
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-756
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.1
>            Reporter: Scott Harrington
>            Assignee: Remko Popma
>            Priority: Trivial
>             Fix For: 2.1
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The PluginManagerPackagesTest runs an embedded JavaCompiler to get the 
> "FixedStringLayout" class that is needed for the test.
> The classpath used by JavaCompiler may or may not have a valid 
> PluginProcessor available. I assume if it did, it would have placed the 
> Log4j2Plugins.dat somewhere in a META-INF subdirectory, but instead (for me) 
> it appears in the current directory, which is log4j-core.
> Simple fix is to add "-proc:none" to the compiler options to disable 
> annotation processing, like this:
> {code:java}
> // compile generated source
> compiler.getTask(null, fileManager, diagnostics, Arrays.asList("-proc:none"), 
> null, compilationUnits).call();
> {code}
> This assumes we really don't need the annotation processing for the test. If 
> we do, then perhaps an explicit classpath needs to be provided to the 
> JavaCompiler so we know we're getting the expected PluginProcessor 
> (presumably one just built moments before). And we would want the test to 
> clean up after itself (remove the DAT file, and probably the compiled classes 
> as well).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to