Re: Not able to pass multiple arguments to javac

2007-11-26 Thread Sahoo
hich are not supported by javac? With regards, Nick Stolwijk -Original Message- From: [EMAIL PROTECTED] on behalf of Sahoo Sent: Mon 11/26/2007 5:12 PM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Yes, I knew that approach, but the options I actually want

Re: Not able to pass multiple arguments to javac

2007-11-26 Thread Wayne Fay
You're > >> trying to add options that are not supported by javac. All javac > >> options are "supported" by the mojo, it simply passes them to javac. > >> > >> Why would you want to add options to javac which are not supported by > >> ja

Re: Not able to pass multiple arguments to javac

2007-11-26 Thread Nick Stolwijk
to javac. Why would you want to add options to javac which are not supported by javac? With regards, Nick Stolwijk -Original Message- From: [EMAIL PROTECTED] on behalf of Sahoo Sent: Mon 11/26/2007 5:12 PM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac

Re: Not able to pass multiple arguments to javac

2007-11-26 Thread Sahoo
Sahoo Sent: Mon 11/26/2007 5:12 PM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Yes, I knew that approach, but the options I actually want to pass are not supported by the mojo. nowarn and verbose were just used as examples; I want to pass -proc:none and -implici

RE: Not able to pass multiple arguments to javac

2007-11-26 Thread nicklist
PROTECTED] Sent: Mon 11/26/2007 5:34 PM To: Maven Users List Subject: RE: Not able to pass multiple arguments to javac The fault message you see is actually from javac itself. You're trying to add options that are not supported by javac. All javac options are "supported" by the mojo,

RE: Not able to pass multiple arguments to javac

2007-11-26 Thread nicklist
regards, Nick Stolwijk -Original Message- From: [EMAIL PROTECTED] on behalf of Sahoo Sent: Mon 11/26/2007 5:12 PM To: Maven Users List Subject: Re: Not able to pass multiple arguments to javac Yes, I knew that approach, but the options I actually want to pass are not supported by t

Re: Not able to pass multiple arguments to javac

2007-11-26 Thread Sahoo
Parameters section of this page: http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sahoo Sent: Monday, November 26, 2007 8:25 AM To: Maven Users List Subject: Re: Not able to pass

RE: Not able to pass multiple arguments to javac

2007-11-26 Thread nicklist
/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html -Original Message- From: Jeff Jensen [mailto:[EMAIL PROTECTED] Sent: Mon 11/26/2007 3:32 PM To: 'Maven Users List' Subject: RE: Not able to pass multiple arguments to javac Try this approach:

RE: Not able to pass multiple arguments to javac

2007-11-26 Thread Jeff Jensen
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sahoo > Sent: Monday, November 26, 2007 8:25 AM > To: Maven Users List > Subject: Re: Not able to pass multiple arguments to javac > > Ignore my earlier email. The suggestion actually do

Re: Not able to pass multiple arguments to javac

2007-11-26 Thread Sahoo
Ignore my earlier email. The suggestion actually does *not* work. When I run with -X option, it shows only the last compilerArgument. See the following output: [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile' --> [DEBUG] (f) basedir = /tmp/my-app [DEBU

Re: Not able to pass multiple arguments to javac

2007-11-26 Thread Sahoo
Thanks, that works. Sahoo Wayne Fay wrote: Try this, Sahoo: org.apache.maven.plugins maven-compiler-plugin -nowarn -verbose On 11/22/07, Sahoo <[EMAIL PROTECTED]> wrote: As suggested in [1], I tried configuring maven-compiler-plugin like this: -nowa

Re: Not able to pass multiple arguments to javac

2007-11-23 Thread Wayne Fay
Try this, Sahoo: org.apache.maven.plugins maven-compiler-plugin -nowarn -verbose On 11/22/07, Sahoo <[EMAIL PROTECTED]> wrote: > As suggested in [1], I tried configuring maven-compiler-plugin like this: > > -nowarn -verbose > > But it causes compilation fail