Build failed in Jenkins: river-qa-refactoring #104

See Changes: [peter_firmstone] River-420 Fixes for unsafe publication by exporting during construction. The low hanging fruit from the qa suite. -- [...truncated 15692 lines...] [java]

Re: Don't export a service from within its contructor

Sounds like a good proposal, River 3.0. Thoughts? Peter. - Original message - > My "startnow" project on java.net, has always provide a "separation" of > construction and start of the service export.  However, the usage of that API > is > supposed to be something like the following. >

Re: QA results

Thanks Bryan, I think the failures are due to my last commit to eliminate exports during construction in the qa suite. I'm relying on Jenkins to run the tests for me, I haven't had time to run them myself. Your help is much appreciated. Regards, Peter. Bryan Thompson wrote: Peter, see be

Build failed in Jenkins: river-qa-refactor-windows #10

See Changes: [peter_firmstone] River-420 Fixes for unsafe publication by exporting during construction. The low hanging fruit from the qa suite. -- [...truncated 15695 lines...] [j

Re: Don't export a service from within its contructor

My "startnow" project on java.net, has always provide a "separation" of construction and start of the service export. However, the usage of that API is supposed to be something like the following. public class MyService extends PersistentJiniService { public static void main( String arg