buildbot failure in on ofbiz-trunk-framework-plugins

The Buildbot has detected a new failure on builder ofbiz-trunk-framework-plugins while building . Full details are available at: https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/143 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: silvanus_ubuntu Build

Re: Failing tests due to bad commits

OK the 2nd test issue is fixed with r1798086 where I reverted my changes in ListFinder.java But as noted in the commit comment I have to check all is correct with current code. Is the created EntityListIterator always closed (in all cases) is still obscure to me. Maybe it's not a big deal

buildbot success in on ofbiz-trunk-framework-plugins

The Buildbot has detected a restored build on builder ofbiz-trunk-framework-plugins while building . Full details are available at: https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/142 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: lares_ubuntu Build

Re: Failing tests due to bad commits

Hi Taher, This is my bad, let me explain why I missed it. I use to rely on Buildbot. Last trunk message was OK https://s.apache.org/Uz5M But I completely forgot that we still need to update our Buildbot config. And actually we still rely on

Re: Information on Design and Structure of Camel Website and Wiki

Thanks Taher. AsciiDoc is designed to translate to Docbook, so all the Docbook ecosystem can be used with AsciiDoc. You can think of AsciiDoc as an alternative syntax to Docbook XML that is more accessible as you write. It feels like you're writing an email. So to my mind our choice is between

Help in reviewing my refactoring of CatalinaContainer

Hey folks, It was very painful and slow, but I finally got a working almost full-rewrite of the CatalinaContainer. I need help with testing, reviews, and code improvements. Details are found in [1]. There are no functional changes, just a rewrite. I appreciate all the help and feedback. [1]

Failing tests due to bad commits

Hey Folks, I have 2 failing tests in the system: - party-tests.testClearAddressMatchMap (Failure) - testPerformFind (Error) So whoever committed this code please look into fixing it. Also let's agree that at a minimum tests should pass with ./gradlew cleanAll loadDefault testIntegration before

Re: Information on Design and Structure of Camel Website and Wiki

Reading through the threads provided by Paul reminded me of the reason why we suffered in making a decision. Documentation is very important, and very boring! I think we all agree now (more-or-less) that documentation inside the code base is probably better. The question to raise (again!) is

Re: Information on Design and Structure of Camel Website and Wiki

Hi all, A reminder AsciiDoc came up in discussions in 2015: http://ofbiz.135035.n4.nabble.com/Some-comments-on-DITA-for-a-small-group-td4670183.html http://ofbiz.135035.n4.nabble.com/Possible-Documentation-and-help-solutions-DITA-td4669377.html Cheers Paul Foxworthy On 8 June 2017 at 17:22,

Re: Information on Design and Structure of Camel Website and Wiki

Hi Zoran Thanks very much for the response. I'll take your feedback back to the OFBiz community as you have highlighted some interesting ideas that could be very useful for us. Thanks Sharan On 2017-06-06 16:12 (+0200), Zoran Regvart wrote: > Hi Sharan, > we use a CI