commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simone Tripodi <>
Subject Re: [chain] Upgrading to Maven parent version 21
Date Sat, 30 Jul 2011 20:23:22 GMT
Hi Elijah,
thanks for putting effort on chain!
Just a silly question: did the test fail also before parent upgrade?
In that case, I'd say i is an error in /trunk.
Unfortunately my new laptop still hasn't arrived so I can't install
everything and check myself, otherwise I would help you a little more
All he best,

On Sat, Jul 30, 2011 at 8:13 PM, Elijah Zupancic <> wrote:
> As part of my refactoring project with Apache Chain, I've been trying
> to update dependency versions. I tried to upgrade the maven parent
> configuration and the compile worked fine, but I have been getting a
> really odd unit test failure. Moreover, I did a diff between maven
> parent pom.xml versions and nothing stood out to me as to why the
> parent pom would cause this.
> Results :
> Failed tests:
> testDefaut(org.apache.commons.chain.config.ConfigParserTestCase)  Time
> elapsed: 0.034 sec  <<< FAILURE!
> junit.framework.AssertionFailedError: Correct command count
> expected:<17> but was:<19>
>        at
>        at junit.framework.Assert.failNotEquals(
>        at junit.framework.Assert.assertEquals(
>        at junit.framework.Assert.assertEquals(
>        at org.apache.commons.chain.config.ConfigParserTestCase.checkCommandCount(
>        at org.apache.commons.chain.config.ConfigParserTestCase.testDefaut(
> The XML file it is reading for commands contains exactly 17 commands,
> so the data source is correct. Before I start to peel apart the XML
> parser, I was wondering if anyone else encountered this before. Do any
> of you have any insight into this?
> Thanks,
> -Elijah
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message