Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 89216 invoked from network); 24 Jun 2009 05:07:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Jun 2009 05:07:03 -0000 Received: (qmail 93995 invoked by uid 500); 24 Jun 2009 05:07:14 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 93901 invoked by uid 500); 24 Jun 2009 05:07:13 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 93893 invoked by uid 99); 24 Jun 2009 05:07:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jun 2009 05:07:13 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of genspring@gmail.com designates 209.85.198.237 as permitted sender) Received: from [209.85.198.237] (HELO rv-out-0506.google.com) (209.85.198.237) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jun 2009 05:07:05 +0000 Received: by rv-out-0506.google.com with SMTP id g9so235905rvb.55 for ; Tue, 23 Jun 2009 22:06:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=MyvdIikTdoeVfwW3xEsMRN1YqzTE4u5vHilHBXC0QTc=; b=YeS4f/WTnZgbcoVWpKbMsJesk9S6ph6chAoTvbXpW+5C+p6k8Sk3NkWBFSQj6+yZcN FACczpylOVzbfWXcPlvK/20RZKUVF7ojJLwuaFLJaXynpR/OnnfV13l10tfXX3uKICzO Y6MzAasXL74MIhOS13VhhVrmpH1+Ojlm/DWEs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=MF6QlmD9Ky5f2h6rd7UTf9bayrNLO+qakhw6xWNfNOaNiBY29o5JUdFQhOSaiipVwC OzJllvK0fvr/W6C1vvBqxpk0om3f8eF9qtIRwcK/4MTfxhC6xjDhYYuuw5IlIzVujRUn FHDd05dP7YJI30RKxZxU7w0xv54b9jsMPGMq4= MIME-Version: 1.0 Received: by 10.140.247.13 with SMTP id u13mr832005rvh.288.1245820005485; Tue, 23 Jun 2009 22:06:45 -0700 (PDT) In-Reply-To: References: <45f744e40906230140o513bd50ge863ed4c589eedc@mail.gmail.com> <6E907CC7-0A0B-4026-BF91-A2A4DC52E75D@yahoo.com> Date: Wed, 24 Jun 2009 13:06:44 +0800 Message-ID: Subject: Re: Suggest to turn off those debug and warning options for maven-compile-plugin From: Shawn Jiang To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary=000e0cd10626e1a574046d111292 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd10626e1a574046d111292 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable 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 > 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 bu= g > 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\gero= nimo\kernel\config\ConfigurationUtil.java:[407,39] > =BE=AF=B8=E6=A3=BA > =D4=DA org.apache.geronimo.kernel.config.Configuration =D6=D0=B5=C4 > getConfigurationResolver() =D2=D1=BE=AD=B2=BB=CC=E1=B3=AB=CA=B9=D3=C3 > Set set =3D > configuration.getConfigurationResolver().resolve(""); > > E:\src\gt\framework\modules\geronimo-kernel\src\main\java\org\apache\gero= nimo\kernel\config\ConfigurationUtil.java:[468,42] > =BE=AF=B8=E6=A3=BA > =D4=DA org.apache.geronimo.kernel.basic.BasicKernel =D6=D0=B5=C4 > getStateReason(org.apache.geronimo.gbean.AbstractName) =D2=D1=BE=AD=B2=BB= =CC=E1=B3=AB=CA=B9=D3=C3 > stateReason =3D ((BasicKernel) > kernel).getStateReason(gbeanName); > > > [INFO] > ------------------------------------------------------------------------ > [DEBUG] Trace > org.apache.maven.BuildFailureException: Compilation failure > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultL= ifecycleExecutor.java:699) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecy= cle(DefaultLifecycleExecutor.java:540) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLi= fecycleExecutor.java:519) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleF= ailures(DefaultLifecycleExecutor.java:371) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(D= efaultLifecycleExecutor.java:332) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecy= cleExecutor.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(DelegatingMethodAccessorI= mpl.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: Compilati= on > 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(DefaultPluginMan= ager.java:483) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultL= ifecycleExecutor.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 t= o > 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 wr= ote: > >> After being initially surprised at the verbosity, I really like the new >> settings. IMO java code is pretty much unusable unless it is compiled w= ith >> 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 the= y >> also caused build failure in my laptop. >> >> true >> true >> true >> true >> >> >> This setting is in release genesis pom: >> genesis\genesis-default-flava\2.0\genesis-default-flava-2.0.pom. So th= at >> we have to override them in server pom.xml. >> >> On Tue, Jun 23, 2009 at 4:40 PM, Ivan wrote: >> >>> HI, >>> No sure why we need to turn on those debug and warning options for t= he >>> 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 ke= ep >>> them ? >>> Thanks ! >>> -- >>> Ivan >>> >> >> >> >> -- >> Shawn >> >> >> > > > -- > Shawn > > > --=20 Shawn --000e0cd10626e1a574046d111292 Content-Type: text/html; charset=GB2312 Content-Transfer-Encoding: quoted-printable
This is a Maven defect definitely, I'll open a JIRA to Maven.=  

Besides, I would try to submit a prob= lem to IBM JDK somewhere about the different behavior. 

=


2009/6/24 David Jencks <david_jencks@yahoo.com>
I have to admit that locale and charact= er 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?
Defau= lt locale: zh_CN, platform encoding: GB18030
Default locale: en_US, platform e= ncoding: 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 w= rote:

This only happens to IBM JDK.=  


----------------------------------------= ------------------------------------------------

\= gt\framework\modules\geronimo-kernel>mvn clean install -X

+ Error stacktraces are turned on.
Apache Mav= en 2.1.0 (r755702; 2009-03-19 03:10:27+0800)
Java vers= ion: 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] =BE=AF=B8=E6=A3=BA
=D4=DA org.apache.geronimo.kernel.config.Configuration =D6=D0=B5= =C4 getConfigurationResolver() =D2=D1=BE=AD=B2=BB=CC=E1=B3=AB=CA=B9=D3=C3
                Set set = =3D configuration.getConfigurationResolver().resolve("");

E:\src\gt\framework\modules\geronimo-kernel\src\main\java= \org\apache\geronimo\kernel\config\ConfigurationUtil.java:[468,42] =BE=AF= =B8=E6=A3=BA
=D4=DA org.apache.geronimo.kernel.basic.BasicKernel =D6=D0=B5=C4 getS= tateReason(org.apache.geronimo.gbean.AbstractName) =D2=D1=BE=AD=B2=BB=CC=E1= =B3=AB=CA=B9=D3=C3
            = ;                stateReason =3D ((= BasicKernel) kernel).getStateReason(gbeanName);


[INFO] --------------------------------= ----------------------------------------
[DEBUG] Trace
= org.apache.maven.BuildFailureException: Compilation failure
 = ;       at org.apache.maven.lifecycle.DefaultLifecycleE= xecutor.executeGoals(DefaultLifecycleExecutor.java:699)
        at org.apache.maven.lifecycle.Defaul= tLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:5= 40)
        at org.apache.maven.lifecycl= e.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
        at org.apache.maven.lifecycle.Defaul= tLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.ja= va:371)
        at org.apache.maven.life= cycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor= .java:332)
        at org.apache.maven.lifecycle.Defaul= tLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
&nb= sp;       at org.apache.maven.DefaultMaven.doExecute(De= faultMaven.java:356)
        at org.apac= he.maven.DefaultMaven.execute(DefaultMaven.java:137)
        at org.apache.maven.cli.MavenCli.mai= n(MavenCli.java:356)
        at sun.refl= ect.NativeMethodAccessorImpl.invoke0(Native Method)
   =      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMe= thodAccessorImpl.java:79)
        at sun.reflect.DelegatingMethodAcces= sorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  =      at java.lang.reflect.Method.invoke(Method.java:618)
        at org.codehaus.classworlds.Launch= er.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher= .launch(Launcher.java:255)
        at or= g.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.ma= in(Launcher.java:375)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compi= lation failure
        at org.apache.mav= en.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
=
        at org.apache.maven.plugin.CompilerMo= jo.execute(CompilerMojo.java:114)
        at org.apache.maven.plugin.DefaultPl= uginManager.executeMojo(DefaultPluginManager.java:483)
 &nbs= p;      at org.apache.maven.lifecycle.DefaultLifecycleExecut= or.executeGoals(DefaultLifecycleExecutor.java:678)
        ... 16 more
[INFO] -------= -----------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Wed Jun 24 10:5= 4:30 CST 2009
[INFO] Final Memory: 25M/79M
[INFO] ----------------------------= --------------------------------------------


<= /div>
-----------------------------------------------------------------= ---------------------------------------------------------------------------= -------------------------



I guess something wrong = when  javac of IBM javac prints the debug/warning messages with <= span style=3D"font-weight:bold">GB18030 Encoding.   here is what I get when using SUN JDK to bulid. The= re's no problem to build.
---------------------------------------------------------------------= ----------------------------------------------------------
=
\gt\framework\modules\geronimo-kernel>mvn clean install -X
+ Error stacktraces are turned on.
Apache Maven 2.1.0 (r755= 702; 2009-03-19 03:10:27+0800)
Java version: 1.5.0_15
J= ava home: D:\dev\JDKs\sun_jdk5\jre
Default locale: en_US, platfor= m encoding: Cp1252




On = Wed, Jun 24, 2009 at 12:28 AM, David Jencks <david_jencks@yahoo.com= > 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 deb= ug info, so I'm +100000000 to keeping the debug flag on.

I have a hard time imagining how showing deprecations and w= arnings 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 fro= m current pom because they also caused build failure in my laptop.

<configuration>
      =      <optimize>true</optimize>
 = ;            <debug>true</debug><= /div>
              <showDep= recation>true</showDeprecation>
                <show= Warnings>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 <xhhs= ld@gmail.com> 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 worksta= tion, maybe it is caused by my local setting.
   Shall we turn them off, or there are some reasons that we nee= d to keep them ?
   Thanks !
--
Ivan



--
Shawn<= br>




--
Shawn




--
Shawn
--000e0cd10626e1a574046d111292--