Deprecated API usage is covered by a different showDeprecated flag.
When I set that flag, I do see deprecated API usage. But I can't
find a way to get the general Java 5 warnings to show up....
-- Adam
On 8/17/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Strange, you should see at least the deprecated API usage.
¬ Simon
"Adam Winer" <[EMAIL PROTECTED]>
2006-08-16 16:48
Please respond to adffaces-dev
To: [email protected]
cc:
Subject: Re: Re: Re: java 5 compliance in jdev
In Maven, there's a showWarnings property of the compiler plugin;
I've turned that on in the Trinidad pom.xml, but I'm not seeing any
warnings. (There's also a command line -D flag too that does
the same thing - same results.)
-- Adam
On 8/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I don't know Maven well enough to answer the question for sure. However
I
> guess it's possible if there's a place to set compiler options. Normally
> the unchecked warnings will show if the options -source 1.5 or -target
1.5
> are present. Since maven compiler is set to 1.5 for Trinidad I guess
those
> options are already used, so what is needed is only a way to see
> compilation warning, not just errors. Is there a
-Dmaven.showWarnings=true
> or something?
>
>
> ¬ Simon
>
>
>
>
>
> "Adam Winer" <[EMAIL PROTECTED]>
> 2006-08-16 13:01
> Please respond to adffaces-dev
>
> To: [email protected]
> cc:
> Subject: Re: Re: java 5 compliance in jdev
>
>
> What I'm out for, actually, is some way to have this checked
> in the Maven build, which is how I do 99% of my work.
> And while I'd never tell a developer that they need to use one
> IDE or another, all Trinidad committers *must* be running the Maven
> build to see if the tests are still passing.
>
> So, can this be done? If not in the actual Maven build, as
> part of a PMD ruleset or something else triggered in site
> generation?
>
> -- Adam
>
>
> On 8/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Hello Gabrielle,
> >
> > I guess Adam and Jeanne will be the most able to answer this question.
> > However, from my experiece, JDeveloper cannot detect the unchecked
> > warnings, e.g. the following unchecked won't be deteted by JDev:
> >
> > public List<String> getStringList();
> >
> > public void myMethod()
> > {
> > List myList = getStringList();
> > }
> >
> > Also, JDeveloper has an issue when autoboxing constants. The following
> was
> > killing the compilation unit when I last tested it with SP2 :
> >
> > public static final Long MY_LONG = 0L;
> >
> > This line is not so nice looking anyway though.
> >
> >
> > Regards,
> >
> > Simon
> >
> >
> >
> >
> >
> > Gabrielle Crawford <[EMAIL PROTECTED]>
> > 2006-08-16 12:30
> > Please respond to adffaces-dev
> >
> > To: [email protected]
> > cc:
> > Subject: java 5 compliance in jdev
> >
> >
> > Hi,
> >
> > I'm testing using the demo bundle and the jdev project created by
> > running mvn jdev:jdev.
> >
> > Does anyone know if there is a way to set something in jdev to check
for
> > java5 compliance when compiling?
> >
> > Thanks,
> >
> > Gabrielle
> >
> >
> >
> >
>
>
>
