[seam-issues] [JBoss JIRA] (SEAM-137) Booking compilation error on IBM JDK 7
Tomas Remes (JIRA)
jira-events at lists.jboss.org
Mon May 14 09:02:18 EDT 2012
[ https://issues.jboss.org/browse/SEAM-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12692634#comment-12692634 ]
Tomas Remes commented on SEAM-137:
----------------------------------
org.jboss.solder.logging.MessageLogger annotation in BookingLog class is probably causing the error. Doing further investigation...
> Booking compilation error on IBM JDK 7
> --------------------------------------
>
> Key: SEAM-137
> URL: https://issues.jboss.org/browse/SEAM-137
> Project: Seam 3 Distribution
> Issue Type: Bug
> Components: Shared Examples
> Affects Versions: 3.1.0.Final
> Environment: IBM J9 VM build 2.6, JRE 1.7.0 Linux x86-32 20110810_88604
> Reporter: Tomas Remes
>
> Cannot compile booking example on IBM JDK 7 because of weird following exception:
> {noformat}
> [ERROR] Failure executing javac, but could not parse the error:
> chyba:Cannot read org.jboss.seam.examples.booking.log package files, cause : java.io.FileNotFoundException: org.jboss.seam.examples.booking.log/BookingLog
> at com.sun.tools.javac.processing.JavacFiler.getResource(JavacFiler.java:476)
> at org.jboss.logging.generator.apt.TranslationClassGenerator.findTranslationFiles(TranslationClassGenerator.java:132)
> at org.jboss.logging.generator.apt.TranslationClassGenerator.processTypeElement(TranslationClassGenerator.java:95)
> at org.jboss.logging.generator.apt.LoggingToolsProcessor.process(LoggingToolsProcessor.java:153)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:805)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:734)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1700(JavacProcessingEnvironment.java:109)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1041)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1175)
> at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1118)
> at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:836)
> at com.sun.tools.javac.main.Main.compile(Main.java:429)
> at com.sun.tools.javac.main.Main.compile(Main.java:343)
> at com.sun.tools.javac.main.Main.compile(Main.java:334)
> at com.sun.tools.javac.Main.compile(Main.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:613)
> at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:554)
> at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
> at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605)
> 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)
> 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:88)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> 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)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list