unfortunately, adding all of this:
<configuration>
<source>1.5</source>
<target>1.5</target>
<fork>true</fork>
<showDeprecation>true</showDeprecation>
<showWarnings>true</showWarnings>
<verbose>true</verbose>
<compilerArgument>-Xlint:unchecked,deprecation,fallthrough,finally</compilerArgument>
</configuration>
still results in nothing for me.
i must be doing something crazy.
is anybody able to see the warnings outside of eclipse?
thanks.
- Cassie
On Wed, Apr 23, 2008 at 5:50 PM, Brian Eaton <[EMAIL PROTECTED]> wrote:
> I see them automatically in Eclipse. There's probably some maven
> trick to have them show up in the build log. (Pause to dig through
> maven documentation...)
>
> http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html
>
> showWarnings=true should do it, I think...
>
> Cheers,
> Brian
>
> On Wed, Apr 23, 2008 at 5:10 AM, Cassie <[EMAIL PROTECTED]> wrote:
> > Sorry for being slow, but how do I get the build warnings to show up? If
> I
> > can get them turned on then I can check this in and fix all of the
> social
> > warnings...
> > Thanks.
> >
> > - Cassie
> >
> >
> >
> > On Tue, Apr 22, 2008 at 7:59 PM, Brian Eaton (JIRA) <[EMAIL PROTECTED]>
> wrote:
> >
> > > fix various build warnings
> > > --------------------------
> > >
> > > Key: SHINDIG-208
> > > URL:
> https://issues.apache.org/jira/browse/SHINDIG-208
> > > Project: Shindig
> > > Issue Type: Bug
> > > Reporter: Brian Eaton
> > > Attachments: warnings.patch
> > >
> > > Got a patch to fix most build warnings, except the generic type issues
> in
> > > the social-api tree. I don't understand some of what that code is
> doing, so
> > > I don't want to change it.
> > >
> > > --
> > > This message is automatically generated by JIRA.
> > > -
> > > You can reply to this email to add a comment to the issue online.
> > >
> > >
> >
>
