On 22 Feb 2011, at 08:50, Simon Pepping wrote: > On Mon, Feb 21, 2011 at 08:28:33PM +0100, Andreas Delmelle wrote: >> I saw one exclusion --unconfirmed cast-- that would seem to stem from my >> recent refactoring in the BlockStackingLMs. Not sure why an exclusion was >> chosen here, but adding an assert statement in the code avoids the warning >> as well *and* has the benefit of being visible exactly at the spot in the >> code where it applies. Seemed like the more proper way to handle this. > > It would be nice if assertions were checked during the junit tests. > However, when I set: <junit ... jvm="java -ea"/>, I get > junit.framework.AssertionFailedError errors. How can this be done?
Sounds like a good idea. IIC, simply using "-ea" would enable internal assertions for JUnit's classes as well. You probably want something like "-ea:org.apache.fop..." to make sure only assertions in FOP's code are taken into account. Regards, Andreas ---