Re: Hot-Deploy in 16.11.04...and Later?

[st...@comcast.net]

In order to be closer to how release 17 will be, would it be advisable to completely avoid the hot-deploy directory for now (this is limited to custom data loading)?
 
----- Original Message -----From: Taher Alkhateeb <sl...@gmail.com>To: user@ofbiz.apache.orgSent: Wed, 31 Jan 2018 23:25:37 -0000 (UTC)Subject: Re: Hot-Deploy in 16.11.04...and Later?

Data loading is one topic, location of custom components is another topic.In release 17 and later, there is no longer a hot-deploy, but only aplugins folder to place your custom work.

As for data loading, it does not matter where you place your component, thedata will load anyway as long as you have the loading in proper order ifyou have any dependencies on other data.

On Feb 1, 2018 1:19 AM, <st...@comcast.net> wrote:

Hi

It was quite some time back (well, a year...that's like 7 dog years or 14programmer years) it was announced that hot-deploy was being deprecated:https://blogs.apache.org/ofbiz/entry/apache-ofbiz-news-march-2017

The directory still exists in 16.11.04. Would it be correct to assume thateven if this still works it would better to make any customization inplugins (mentioned in the above URL)? And would this be true of customcomponent loads of data when nothing else is being customized, or is dataload customization a completely different topic for building custom gradlewload targets?

Thanks!