enabling and disabling assertions

[Aakash Goel]

if I say

java  -da:com.foo... -ea myclass

Won't it be equivalent to

java -ea myclass

Just want to confirm this.

[Devaka Cooray]

Yes it is equivalent to the first one.

[avi sinha]

Devaka Cooray wrote:Yes it is equivalent to the first one.

how is this possible sir?

first statement is enabling assertion for all except com.foo package

and the secondone is enabling all. am i correct??

avi

[Aakash Goel]

thanks devaka. So, the order matters

@avi, in java -da:com.foo... -ea myclass

what I get is that, you first selectively disable assertions, but then enable all the assertions.

[Lucas Smith]

I think it is equivalent - in Java 6 assertions are disabled by default

[Devaka Cooray]

avi sinha wrote:
first statement is enabling assertion for all except com.foo package

and the secondone is enabling all. am i correct??

You are very right, here.
I was wrong with my previous message, oops my eyes.

If an assertion argument found either with a package name or with a class name, it will be perceived as more specific than the general (no argument) assertion. In this case it does NOT depend with order of assertion arguments. Therefore...

java -da:com.foo... -ea myclass
is equivalent to
java -ea -da:com.foo... myclass


Devaka.