Niall Pemberton wrote:
On 11/29/05, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On 11/29/05, Laurie Harper <[EMAIL PROTECTED]> wrote:
Niall Pemberton wrote:
Also looked like the property types were the wrong way round for
indexed methods, so I also switched them.
Hmm, with that change, accessing a List property is broken. Without the
change, all my tests are working. You can deploy the exercises app with
the addition I just committed and see for yourself:
http://localhost:8080/struts-examples/exercise/enhanced-dynabean.do
I've rolled back your change and everything works fine again, including
indexed property access for arrays and lists. The unit test you added
passes either way.
I just refreshed and the JUnit test I wrote is now failing for me.
Its failing in gump as well
http://vmgump.apache.org/gump/public/struts/struts-action/gump_work/build_struts_struts-action.html
I've had problems with the maven build - when I've used build-all if a
sub-project test fails maven just carries on ignoring it and it
appears you get a successful build. Now I do the sub-projects
separately.
I'm wondering if thats what you used?
I was using 'maven test' without problem. It seems my checkout was
warped, though, because even though svn was telling me it was
up-to-date, after an 'svn update' I'm now seeing the failure.
I'll look at it tomorrow and figure out what's wrong.
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
