Page History

...

Now about the 1st build-dev target: sometimes you don't even create any hot-deploy components (eg. some projects might use OFBiz as a web services API with few modifications in OFBiz core) or you need to put patches somewhere before creating a hot-deploy-component. Then to keep your OFBiz working copy free from modifications (which could else been put in one of your hot-deploy components patches directory, which is anyway not very logical but pragmatic),  you put your paches in the runtime/patches folder where "core" patches (those which change OFBiz as it's OOTB) are supposed to be. "build-dev" is purposely independent of any other target but makes sense to be called before the main build target. The idea for the build-dev target is to keep patches with features separated (ie grouping different files changed for a feture in a patch), but you can, or may have to, do it on a file level, notably when 2 or more features impact the same file...

Then later, if you need to differentate thes files on different areas (URLs, ports in entityengine.xml comes to mind) you can move/duplicate them under the patches/test|qa|production directories of a hot-deploy component of your choice.

Extending an Existing webapp Only

...