This is not good.
They should both be processed in the same way.
Raise a bug report in Jira.
--
dIon Gillard, Multitask Consulting
Frederic Gedin [EMAIL PROTECTED] wrote on 12/05/2004 06:42:40 PM:
Frederic Gedin a écrit :
Hello
I am facing a problem with maven junit plugin:
I put some asserts inside my code and gave the following options in
the project.properties file:
maven.junit.fork=true
maven.junit.jvmargs=-ea
When running maven -X test, I clearly see that the JVM is invoked
with the -ea option. However when I invoke maven -X -D
testmach=TestSingle test:match, the JVM is invoked without the
-ea options my asserts do not generate any exception.
Is this a known bug or a know restriction?
Digging a little bit into the plugin code, I realized that jvm args are
not processed the same way in both cases:
goals test:test and test:single
u:tokenize var=listOfJvmArgs delim=
${maven.junit.jvmargs}/u:tokenize
j:forEach var=somejvmarg items=${listOfJvmArgs}
jvmarg value=${somejvmarg}/
/j:forEach
goal test:match
maven:pluginVar var=jvmargs plugin=maven-test-plugin
property=maven.junit.jvmargs /
j:if test=${!empty(jvmArgs)}
jvmarg line=${jvmargs}/
/j:if
While not being aware of jelly coding, I suspect that the test:match
goal should be coded the same as test:test and test:single.
If yes, how can I put the fix back ?
Regards
Frederic
-
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]
