well, we talked about it several times IIRC. The main point was community - while we are not enough splitting would add work for everyone + inconsistency in releases. Only things we could extract would be related to no more developed modules.
If we look we have more or less: - openejb container - openejb server - tomee - maven - arquillian (other modules are more or less directly related to these one) All these modules have got develoment between last release and next one. The easiest to split would be server part where several modules are not touched anymore but they are small enough to be kept. So globally not sure we and users would benefit from it. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-05-04 16:33 GMT+02:00 Andy Gumbrecht <[email protected]>: > I think we're getting to a point where we should be thinking about how we > can split things down a bit. There are several areas that are really stable > and others that are really eating time. Wdyt? > > -- > Andy Gumbrecht http://www.tomitribe.com > TomEE treibt Tomitribe! > Sent from my mobile device. Please excuse my brevity. > > On May 4, 2014 3:04:05 PM CEST, Romain Manni-Bucau <[email protected]> > wrote: >> >> PS: we test plum distro too now which had a bunch of time too >> >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> 2014-05-04 13:50 GMT+02:00 Romain Manni-Bucau <[email protected]>: >>> >>> we were at about 3h10 IIRC, buildbot is surely more used than before >>> it breaks so maybe nothing important >>> >>> >>> Romain Manni-Bucau >>> Twitter: @rmannibucau >>> Blog: http://rmannibucau.wordpress.com/ >>> LinkedIn: http://fr.linkedin.com/in/rmannibucau >>> Github: https://github.com/rmannibucau >>> >>> >>> 2014-05-04 12:58 GMT+02:00 Andy Gumbrecht <[email protected]>: >>>> >>>> Just looking at the logs it looks like a runaway process, but also no >>>> definitive point. Just lots of IO on files, and that's usually a >>>> culprit if >>>> they're not getting closed. Also sockets on linux. Also, that last >>>> build >>>> took 4hrs? >>>> >>>> -- >>>> Andy Gumbrecht http://www.tomitribe.com >>>> TomEE treibt Tomitribe! >>>> Sent from my mobile device. Please excuse my brevity. >>>> >>>> >>>> On May 4, 2014 12:33:39 PM CEST, Romain Manni-Bucau >>>> <[email protected]> >>>> wrote: >>>>> >>>>> >>>>> what i never found was if it was debian or previous processes, any >>>>> idea? >>>>> >>>>> >>>>> Romain Manni-Bucau >>>>> Twitter: @rmannibucau >>>>> Blog: http://rmannibucau.wordpress.com/ >>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau >>>>> Github: https://github.com/rmannibucau >>>>> >>>>> >>>>> 2014-05-04 11:33 GMT+02:00 agumbrecht <[email protected]>: >>>>>> >>>>>> >>>>>> It seems the Debian packaging is thrashing the file system. >>>>>> >>>>>> Something in there is not closing streams properly and also the >>>>>> logging >>>>>> is >>>>>> consuming a lot of bandwidth. >>>>>> >>>>>> Andy. >>>>>> >>>>>> >>>>>> >>>>>> ----- >>>>>> -- >>>>>> Andy >>>>>> Gumbrecht >>>>>> >>>>>> http://www.tomitribe.com >>>>>> [email protected] >>>>>> https://twitter.com/AndyGeeDe >>>>>> >>>>>> TomEE treibt Tomitribe ! | http://tomee.apache.org >>>>>> -- >>>>>> View this message in context: >>>>>> >>>>>> http://openejb.979440.n4.nabble.com/Too-Many-Open-Files-tp4669130.html >>>>>> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
