Sorry, false alarm. I missed an update when I built that version of
maven locally.
Benjamin Bentmann wrote:
John Casey wrote:
and I have:
[...]
stringParams.1=test
stringParams=2
stringParams.0=test
[...]
Which expresses the bug MNG-4023 is about, i.e. the profile from the
test parent POM
John Casey wrote:
and I have:
[...]
stringParams.1=test
stringParams=2
stringParams.0=test
[...]
Which expresses the bug MNG-4023 is about, i.e. the profile from the
test parent POM was injected two times instead of only once.
I try to catch you in IRC later this day so we can have a close
It's fine for me
On 10/02/2009, at 6:01 AM, John Casey wrote:
Actually, it looks like the properties are coming out wrong.
It looks for:
assertEquals( "1", props.getProperty( "stringParams" ) );
assertEquals( "test", props.getProperty( "stringParams.0" ) );
assertEquals( null, props.getProper
Actually, it looks like the properties are coming out wrong.
It looks for:
assertEquals( "1", props.getProperty( "stringParams" ) );
assertEquals( "test", props.getProperty( "stringParams.0" ) );
assertEquals( null, props.getProperty( "stringParams.1" ) );
and I have:
[...]
stringParams.1=tes
Hi,
I was wondering whether others have seen failures in this integration
test (MNG-4023). It's failing consistently on my machine, and I'm simply
calling the bootstrap with integration tests as follows:
ant with-its
I haven't dug into this too far, but it looks like the log.txt file (the
b
