|
So, to understand the elements of the description correctly:
#1 is utilising the logic (code) used for components/applications in the hot-deploy folder to start these components and applications there, and apply that logic to the into plugins renamed special purpose folder?
#2 is the pullPluginSource task basically a copy/paste action similar adopters have to perform to get components/applications into the hot-deploy folder?
#3 is basically removing the component-load.xml form the renamed special purpose folder making the plugin folders behaving the same as the hot-deploy folder?
Would it therefore not have been more prudent, and effort and time saving, to think through the concepts of this whole 'plugin' approach more thoroughly than to have this community go through al lot of confusion and conflict to arrive to at what basically is:
#1 the hot-deploy folder for special purpose components and applications;
#2 moving components/applications in the now renamed special purpose folder out of the OFBiz trunk, future release branches and releases and into attic?
|
Locked
