Is this a bug for the maven.junit.jvmargs?
Sincerely,
Ming Cheung
WebSphere Web Services Developer
Address: IBM, Inc. 11501 Burnet Road, Austin, TX 78758
Tie Line: 678-0733
Email: [EMAIL PROTECTED]
Ming Cheung/Austin/[EMAIL PROTECTED]
08/29/2006 04:08 PM
|
|
Hi Arnaud,
The the java security debug is not showing afte add the following 3 properties to project.properties file.
maven.junit.fork=true
maven.junit.forkmode=perTest
maven.junit.jvmargs=-Djava.security.debug=all
Sincerely,
Ming Cheung
WebSphere Web Services Developer
Address: IBM, Inc. 11501 Burnet Road, Austin, TX 78758
Tie Line: 678-0733
Email: [EMAIL PROTECTED]
"Arnaud HERITIER" <[EMAIL PROTECTED]>
08/29/2006 05:30 AM
|
|
If you don't fork your tests you have to set these options in the
environment variable MAVEN_OPTS.
If fork is enabled you have to use the property maven.junit.jvmargs
http://maven.apache.org/maven-1.x/plugins/test/properties.html
Arnaud
On 8/28/06, Ming Cheung <[EMAIL PROTECTED]> wrote:
>
>
>
> I am using maven 1.1-beta 3. When I added the
> -Dmaven.junit.jvmargs=-Djava.security.debug=all, I am unable to see the
> debug information. Could someone please tell me how to pass jvm arguments
> [ie. -Djava.security.debug=all] to a test/project/junit test?
>
> Sincerely,
>
> Ming Cheung
> WebSphere Web Services Developer
>
> Address: IBM, Inc. 11501 Burnet Road, Austin, TX 78758
> Tie Line: 678-0733
> Email: [EMAIL PROTECTED]
>
