On 21/06/11 01:16, Lavoie, John L wrote: > I found this message in the archives: > > http://sourceforge.net/mailarchive/message.php?msg_id=26211662 > > Has there been any update on it? What about a workaround?
Here's a quick update of where we are on this -all problems with spaces in the ant command line (and in the .sf files #includes) have -we believe- been fixed. You can check out the code and try it to see if this is the case -the finishing of the sf-run work is still outstanding; it'll have to wait until Julio comes back from his vacation. Assuming the problem is easy to fix, that would put the release date for a new version of SmartFrog to the week of July 5. There's been some big changes to test running framework recently, to deal with some race conditions, so if anyone is using the TestBlock/TestCompound/xunit code and/or explicitly running deployments from Junit, they are strongly encouraged to check out before the release and make sure that nothing has broken with this: http://jira.smartfrog.org/jira/browse/SFOS-1604 the key change is that unless you set runTests true in these components, the tests will only run if a new method in the TestBlock interface is called to trigger the test run, rather than have them start automatically. This works around a race condition in which the test target would complete its lifecycle before the junit test runner had a chance to bind to it. -Steve ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Smartfrog-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/smartfrog-users
