Taher, all, If we all are in favour to remove the component-load .xml everywhere, and leave component dependencies to the list of components in <depend-on component-name="?,??,???"> then we need to revisit the gradle task 'loadDefault' too. Currently that task loads demo data by default (and that requires a specific load order). The same also applies to the function(s) related to XML Data Import Readers.
Best regards, Pierre Smits ORRTIZ.COM <http://www.orrtiz.com> OFBiz based solutions & services OFBiz Extensions Marketplace http://oem.ofbizci.net/oci-2/ On Thu, Dec 1, 2016 at 11:14 AM, Pierre Smits <pierre.sm...@gmail.com> wrote: > For what it is worth: the component-load.xml file solely exists to > facilitate how demo data is loaded. > > Best regards, > > Pierre Smits > > ORRTIZ.COM <http://www.orrtiz.com> > OFBiz based solutions & services > > OFBiz Extensions Marketplace > http://oem.ofbizci.net/oci-2/ > > On Thu, Dec 1, 2016 at 11:08 AM, Jacopo Cappellato <jacopo.cappellato@ > hotwaxsystems.com> wrote: > >> On Thu, Dec 1, 2016 at 10:35 AM, Taher Alkhateeb < >> slidingfilame...@gmail.com >> > wrote: >> >> > [...] >> > So my suggestion to move forward in the plugin system is to: >> > - Rename /specialpurpose to /plugins >> > >> >> +1 >> >> >> > - remove /plugins/component-load.xml >> > >> >> +1 >> >> >> > - Refactor gradle to 1) not load a component if enabled="false" and 2) >> if a >> > component directory does not have a component-load.xml then load >> everything >> > >> >> +1 >> >> Thank you Taher, this looks great to me. >> >> Jacopo >> > >
