The r13.07 branch and its releases are painful to everybody (and more importantly our new adopters) as they don't find in the releases what is advertised elsewhere in projects web and wiki pages. This has been shown in various threads in the user ml. And this keeps going on as long as we keep r13.07 as the basis of 'latest stable release'.
Best regards, Pierre Smits *OFBiz Extensions Marketplace* http://oem.ofbizci.net/oci-2/ On Tue, Nov 10, 2015 at 5:54 AM, <[email protected]> wrote: > Hi Nicolas, > > The 13.07 to me was a painful release to deal with because of stripping > out the specialpurpose components. Also disabling these components means > lower quality, no testing and no guarantee of being compatible with the > current version of trunk. So i would imagine this to be sort of equivalent > to killing these components some of which i find very useful like BIRT, > project management and ecommerce. > > This topic was heavily discussed in the past and I think a solution like > turning off the components is very quick indeed but not ideal. > > Taher Alkhateeb > > > On Nov 10, 2015, at 12:40 AM, Nicolas Malin <[email protected]> > wrote: > > > > Hello, > > > > With some latest great discussion about keep or not keep specialpurpose > components on branch, I some inconvenience come from that a specialpurpose > can be overload the definition (service, entity or something like that) > present on application component. > > > > It's easier, we can comment all lines present on > specialpurpose/component-load.xml and if some people want use a specific > component, just uncomment it :) > > > > I see two advantages : > > * detect bad depends easily (a application or framework that use > specialpurpose) > > * detect if a component it on the good place > > > > Your comments ? > > > > Nicolas >
