[jboss-jira] [JBoss JIRA] Commented: (LOGTOOL-23) Seems to be an XNIO bug with the processor and JDK7
[
https://issues.jboss.org/browse/LOGTOOL-23?page=com.atlassian.jira.plugin...
]
James Perkins commented on LOGTOOL-23:
--------------------------------------
A couple notes to add. A patch is in the upstream of of IcedTea7
(http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=767).
There is also a work-around for the Oracle JDK7 and OpenJDK7. The argument
-AtranslationFilesPath can be used to pass the full base path to the translation files.
Here is an example of how the argument can be used in a maven project:
<build>
...
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<compilerArgument>
-AtranslationFilesPath=${project.basedir}/src/main/resources/
</compilerArgument>
</configuration>
</plugin>
...
</plugins>
...
</build>
Seems to be an XNIO bug with the processor and JDK7
---------------------------------------------------
Key: LOGTOOL-23
URL: https://issues.jboss.org/browse/LOGTOOL-23
Project: Log Tool
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: James Perkins
Assignee: James Perkins
The error appears to be in com.sun.tools.javac.files.JavacFilerManager.
error: Cannot read org.jboss.logging.test package files, cause :
java.io.FileNotFoundException: org.jboss.logging.test/ExtendedBasicLogger
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:613)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
error: Cannot read org.jboss.logging.test package files, cause :
java.io.FileNotFoundException: org.jboss.logging.test/ExtendedBasicLogger
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:656)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira