|
|
|
[
Permlink
| « Hide
]
Matt Raible - 01/May/07 11:36 PM
If you run "mvn -Dcargo.wait" and do the steps that WebTest does manually in your browser, what do you see? Are you using M5-SNAPSHOT?
Finally had a chance to follow up on this today...
Yes, I am using M5-SNAPSHOT and when I ran the tests today it updated several versions of dependencies. When I run "mvn -Dcargo.wait" I get "build successful" but no container is started. When I run "mvn -Dcargo.wait integration-test" Tomcat launches and is listening on 8081, but any requests I make to it returns a blank page [which seems weird to me ;) ] So I tried it running "mvn jetty:run-war"... The test that is failing is the password hint. It appears that the test may still be looking for the user "mraible" but the sample-data.xml loads "admin". Sorry, the command should be "mvn -Dcargo.wait=true integration-test". As far as the bad username in sample-data.xml, I changed this in Subversion a couple nights ago.
"mvn -Dcargo.wait=true integration-test" has the same effect as "mvn -Dcargo.wait integration-test". I may have a configuration issue? But in any case I was able to reproduce the issue in Jetty.
This comment that was posted directly to the issues mail list: hiugong.gwok@... : "src/test/resources/login.xml has user name and password hard-coded, and it won't be overwrited during update." I think Hiugong is right, my login.xml is wrong not sample-data.xml. It sounds to me like I may have created my project at just the wrong time where you were in the middle of changing the user/password combinations, but were not quite done at the time. I deleted the whole project and re-create it from today's M5-SNAPSHOT. Now everything works as expected. I'll update the bug report accordingly. This bug was a temporary problem caused by an incomplete commit.
|
||||||||||||||||||||||||||||||||||||||||