I filed a JIRA to maven compiler plugin about this problem: http://jira.codehaus.org/browse/MCOMPILER-100
FYI. 2009/6/24 Shawn Jiang <[email protected]> > This is a Maven defect definitely, I'll open a JIRA to Maven. > > Besides, I would try to submit a problem to IBM JDK somewhere about the > different behavior. > > > > 2009/6/24 David Jencks <[email protected]> > > I have to admit that locale and character encoding issues are something I >> know almost nothing about. >> I think this is likely a bug in either maven or the IBM compiler, but I >> have no idea how to figure out which. >> >> Do you know why these are different with the different jdks? >> >> Default locale: *zh_CN, platform encoding: GB18030* >> >> Default locale: en_US, platform encoding: Cp1252 >> >> >> Is there some way to make everything use utf-8? >> >> If you can figure out anything that makes it seem like this is a maven bug >> I hope you will file a maven jira :-) >> >> thanks >> david jencks >> >> On Jun 23, 2009, at 8:20 PM, Shawn Jiang wrote: >> >> This only happens to IBM JDK. >> >> >> >> ---------------------------------------------------------------------------------------- >> >> \gt\framework\modules\geronimo-kernel>mvn clean install -X >> >> + Error stacktraces are turned on. >> Apache Maven 2.1.0 (r755702; 2009-03-19 03:10:27+0800) >> Java version: 1.5.0 >> Java home: d:\dev\JDKs\ibm_jdk5\jre >> Default locale: *zh_CN, platform encoding: GB18030* >> >> >> ......... >> >> E:\src\gt\framework\modules\geronimo-kernel\src\main\java\org\apache\geronimo\kernel\config\ConfigurationUtil.java:[407,39] >> 警告： >> 在 org.apache.geronimo.kernel.config.Configuration 中的 >> getConfigurationResolver() 已经不提倡使用 >> Set set = >> configuration.getConfigurationResolver().resolve(""); >> >> E:\src\gt\framework\modules\geronimo-kernel\src\main\java\org\apache\geronimo\kernel\config\ConfigurationUtil.java:[468,42] >> 警告： >> 在 org.apache.geronimo.kernel.basic.BasicKernel 中的 >> getStateReason(org.apache.geronimo.gbean.AbstractName) 已经不提倡使用 >> stateReason = ((BasicKernel) >> kernel).getStateReason(gbeanName); >> >> >> [INFO] >> ------------------------------------------------------------------------ >> [DEBUG] Trace >> org.apache.maven.BuildFailureException: Compilation failure >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:699) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:618) >> at >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >> at >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >> Caused by: org.apache.maven.plugin.CompilationFailureException: >> Compilation failure >> at >> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516) >> at >> org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) >> at >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) >> ... 16 more >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 8 seconds >> [INFO] Finished at: Wed Jun 24 10:54:30 CST 2009 >> [INFO] Final Memory: 25M/79M >> [INFO] >> ------------------------------------------------------------------------ >> >> >> >> --------------------------------------------------------------------------------------------------------------------------------------------------------------------- >> >> >> >> I guess something wrong when javac of IBM javac prints the debug/warning >> messages with GB18030 Encoding. here is what I get when using SUN JDK >> to bulid. There's no problem to build. >> >> ------------------------------------------------------------------------------------------------------------------------------- >> \gt\framework\modules\geronimo-kernel>mvn clean install -X >> + Error stacktraces are turned on. >> Apache Maven 2.1.0 (r755702; 2009-03-19 03:10:27+0800) >> Java version: 1.5.0_15 >> Java home: D:\dev\JDKs\sun_jdk5\jre >> Default locale: en_US, platform encoding: Cp1252 >> >> >> >> >> On Wed, Jun 24, 2009 at 12:28 AM, David Jencks <[email protected]>wrote: >> >>> After being initially surprised at the verbosity, I really like the new >>> settings. IMO java code is pretty much unusable unless it is compiled with >>> debug info, so I'm +100000000 to keeping the debug flag on. >>> I have a hard time imagining how showing deprecations and warnings could >>> cause a build error. Can you provide more details? >>> >>> thanks >>> david jencks >>> >>> On Jun 23, 2009, at 2:46 AM, Shawn Jiang wrote: >>> >>> Agree to turn off debug and warning options from current pom because they >>> also caused build failure in my laptop. >>> <configuration> >>> <optimize>true</optimize> >>> <debug>true</debug> >>> <showDeprecation>true</showDeprecation> >>> <showWarnings>true</showWarnings> >>> </configuration> >>> >>> This setting is in release genesis pom: >>> genesis\genesis-default-flava\2.0\genesis-default-flava-2.0.pom. So that >>> we have to override them in server pom.xml. >>> >>> On Tue, Jun 23, 2009 at 4:40 PM, Ivan <[email protected]> wrote: >>> >>>> HI, >>>> No sure why we need to turn on those debug and warning options for >>>> the maven-compile-plugin, it made much outputs in the building process. >>>> And, it caused the compile failure on my workstation, maybe it is >>>> caused by my local setting. >>>> Shall we turn them off, or there are some reasons that we need to >>>> keep them ? >>>> Thanks ! >>>> -- >>>> Ivan >>>> >>> >>> >>> >>> -- >>> Shawn >>> >>> >>> >> >> >> -- >> Shawn >> >> >> > > > -- > Shawn > -- Shawn
