See also https://issues.apache.org/jira/browse/OFBIZ-8229
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:56 AM, Pierre Smits <[email protected]> wrote: > Taher, > > For insights about what the load order in the special purpose folder is, > see the component-load.xml file in that folder. > For insights on where the dependencies exists, please visit the wiki page > Jacques mentioned earlier and search the various open issues in JIRA about > moving demo data from special purpose to application components (there is a > huge dependency on demo data in the ecommerce component for e.g. test > purposes. > > The loadDefault task loads demo data by default, which requires the > specific load-order. The same applies to loading demo data through the XML > Import Data Readers in the DevOps component. > > 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:39 AM, Taher Alkhateeb < > [email protected]> wrote: > >> Hi Pierre, >> >> What is the load order in /specialpurpose, what depends on what? Also what >> should we revisit about loadDefault and load readers? >> >> Taher Alkhateeb >> >> On Thu, Dec 1, 2016 at 1:31 PM, Pierre Smits <[email protected]> >> wrote: >> >> > 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 <[email protected]> >> > 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 < >> > >> [email protected] >> > >> > 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 >> > >> >> > > >> > > >> > >> > >
