Re: Disabling some of the specialpurpose components

2013-04-06 Thread Medhat AbdelBadie
+1 Medhat On Fri, Apr 5, 2013 at 4:52 PM, Jacopo Cappellato < jacopo.cappell...@hotwaxmedia.com> wrote: > We have recently discussed the idea of keeping all the specialpurpose > components in the trunk, remove them from future release branches (starting > with 13.04 that will probably still con

Re: Disabling some of the specialpurpose components

2013-04-06 Thread Jacopo Cappellato
In revision 1465250 I have disabled crowd. Good news Hans: this time it didn't require much of my work and I was able to save the birt component by copying to it the old Axis 1 jars (in rev. 1465252); so we can keep it enabled and it will still compile and run even if the framework is no more us

Re: Disabling some of the specialpurpose components

2013-04-06 Thread Hans Bakker
for birt -1 regards, Hans On 04/05/2013 09:52 PM, Jacopo Cappellato wrote: We have recently discussed the idea of keeping all the specialpurpose components in the trunk, remove them from future release branches (starting with 13.04 that will probably still contain the ecommerce component becau

Re: Disabling some of the specialpurpose components

2013-04-05 Thread Jacques Le Roux
+1 Jacques From: "Jacopo Cappellato" > We have recently discussed the idea of keeping all the specialpurpose > components in the trunk, remove them from future release branches (starting > with 13.04 that will probably still contain the ecommerce component because a > lot unit tests are based

Disabling some of the specialpurpose components

2013-04-05 Thread Jacopo Cappellato
We have recently discussed the idea of keeping all the specialpurpose components in the trunk, remove them from future release branches (starting with 13.04 that will probably still contain the ecommerce component because a lot unit tests are based on demo data in it and because of some other mi