Good discussion for sure. IMO, no one would like to use Trunk for an ongoing development of custom apps. Choosing an official release helps here.
OFBiz is going through a major phase of improvements and all of these are being done only in trunk, which is perfectly fine. If you are subscribed to OFBiz Wiki(Confluence) Daily Updates, you will observe there are ongoing changes to the documentation being taken care of. I agree that there will be some effort required to keep it up to date and to make it ready for future releases. We should define a documentation framework as well, that can be maintained along with the code in trunk, which is available to users when a specific release is announced. When one application is to upgraded to any of the latest releases of OFBiz, there are definitely a bunch of changes you have to take care of, this time it would require some changes to the placement of custom applications, which is not going to be a big effort. In the software world, making a small change is a big deal when it has many users, but sometimes you have to take the risks because it's going to benefit users in future. I personally have witnessed long email threads on dev list before making these changes in directory structures or replacement of tools like from ant to gradle. So yes IMHO, change is always not that easy. Best regards, Pranay Pandey Senior Manager, Enterprise Software Development HotWax Systems http://www.hotwaxsystems.com/ On Tue, Apr 25, 2017 at 12:23 AM, Taher Alkhateeb < [email protected]> wrote: > Hi Skip, > > If you check trunk, you will notice that hot-deploy is removed and > specialpurpose is renamed to plugins and it is _empty_ > > On Apr 24, 2017 9:41 PM, "Skip" <[email protected]> wrote: > > > > > james yong wrote "The special-purpose and hot-deploy folders are > > essentially > > combined into a > > plugins folder which is easier understood by new users, in my own > opinion." > > > > I disagree strongly with this statement. Historically, special-purpose > was > > just that, components which are not generally used by most users. > > hot-deploy is (was) used by nearly everyone to put custom components used > > by > > their application. > > > > Having a single plugin folder that combines both hot-deploy and > > special-purpose seems to me to be a very bad idea. Why not just rename > > hot-deploy to plugin and leave special-purpose as it is. Makes directory > > management much easier to not have the 20 odd components in > special-purpose > > combined with the few in hot-deploy. > > > > > > Skip > > > > > > >
