Re: Suggest to turn off those debug and warning options for maven-compile-plugin

[David Jencks]

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 <xhh...@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 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