RE: [m2] maven-surefire-plugin 2.1.3 vs 2.2

2007-01-18 Thread Dário Luís Coneglian Oliveros
I noticed maven-surefire-plugin 2.1.3 uses forkMode='none' and 
childDelegation='true' as default.
However If I add the same configuration to maven-surefire-plugin 2.2, my tests 
don't work. Since I use javolution.jar as a test dependency and it overrides 
some classes from java.lang.reflect, I get a 'prohibited package name' error. 
The same problem does not happen to 2.1.3.
Any thoughts ? Any idea where to look at ?

Dário



-Original Message-
From: Dário Luís Coneglian Oliveros 
Sent: quarta-feira, 17 de janeiro de 2007 16:13
To: Maven Users List (E-mail)
Subject: [m2] maven-surefire-plugin 2.1.3 vs 2.2


I have some test cases that used to work with maven-surefire-plugin 2.1.3, but 
not with 2.2.
Does anybody know what kind of configuration should be in 2.2 to get the same 
behaviour as of 2.1.3 ?
I've tried a couple of them (forkMode=never, childDelegation=true), but could 
not get anything working.
Any help is appreciated.
Dário

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [m2] maven-surefire-plugin 2.1.3 vs 2.2 [solved]

2007-01-18 Thread Dário Luís Coneglian Oliveros
I just figured out my test cases were failing because the geotools map 
transformation used by them does not work when assertions are enabled. Since 
maven-surefire-plugin enables them by default, I had to add the following 
configuration to the plugin.

...
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.2/version
configuration
  argLine-disableassertions:org.geotools.../argLine
/configuration
  /plugin
...

Hope someone find this info useful.
Dário

-Original Message-
From: Dário Luís Coneglian Oliveros 
Sent: quinta-feira, 18 de janeiro de 2007 09:35
To: Maven Users List
Subject: RE: [m2] maven-surefire-plugin 2.1.3 vs 2.2


I noticed maven-surefire-plugin 2.1.3 uses forkMode='none' and 
childDelegation='true' as default.
However If I add the same configuration to maven-surefire-plugin 2.2, my tests 
don't work. Since I use javolution.jar as a test dependency and it overrides 
some classes from java.lang.reflect, I get a 'prohibited package name' error. 
The same problem does not happen to 2.1.3.
Any thoughts ? Any idea where to look at ?

Dário



-Original Message-
From: Dário Luís Coneglian Oliveros 
Sent: quarta-feira, 17 de janeiro de 2007 16:13
To: Maven Users List (E-mail)
Subject: [m2] maven-surefire-plugin 2.1.3 vs 2.2


I have some test cases that used to work with maven-surefire-plugin 2.1.3, but 
not with 2.2.
Does anybody know what kind of configuration should be in 2.2 to get the same 
behaviour as of 2.1.3 ?
I've tried a couple of them (forkMode=never, childDelegation=true), but could 
not get anything working.
Any help is appreciated.
Dário

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[m2] maven-surefire-plugin 2.1.3 vs 2.2

2007-01-17 Thread Dário Luís Coneglian Oliveros
I have some test cases that used to work with maven-surefire-plugin 2.1.3, but 
not with 2.2.
Does anybody know what kind of configuration should be in 2.2 to get the same 
behaviour as of 2.1.3 ?
I've tried a couple of them (forkMode=never, childDelegation=true), but could 
not get anything working.
Any help is appreciated.
Dário

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]