Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

GOAL: draft for a quick start guide to set up a simple strategy that allows you to maintain a customized version of OFBiz under SVN revision control and synchronized with the standard OFBiz SVN.

...

Note
  • This strategy is a simple implementation of the Vendor Branch Pattern; for more details about Vendor Branches refer to the "Version Control with Subversion" manual (see here)
  • Here is a specific simple strategy for Windows
  • Note that most of advanced users (notably committers) prefer to directly work with the trunk following this strategy

Overview: The plan is to develop a customized version of OFBiz called customofbiz, but we want to stay up to date with the official OFBiz development. We will target to do the update once every month but it can be done at any point in time.Stage 1:

  1. Get OFBiz from the official Apache SVN server (let's say r482800 - this in no way suggests that revision is good, bad or otherwise it's just a number);

...

  1. Import it into the local SVN repository as the ofbiz project; and tag it as ofbiz r482800;

...

  1. Use it as the base for my customofbiz project making changes as needed to do the customisation.

...

  1. Next month get the latest OFBiz revision, let's say r483333, from the official Apache SVN and update the local ofbiz project in the local repository with it (also adding a tag to it, for example ofbiz r483333).

...

  1. Finally do a merge between ofbiz r482800, ofbiz r483333 and my working copy (containing the up to date customofbiz project), resolve the conflicts and commit everything to the local customofbiz.

...

Repository structure

Here is the local repository structure to maintain:
ofbiz
ofbiz/current ---> this will contain the latest official OFBiz release
ofbiz/ofbiz-<revnumA> ---> these are the monthly tags for the official OFBiz release (e.g. ofbiz-r482800, ofbiz-r483333, etc...)
ofbiz/ofbiz-<revnumB>
...
ofbiz/ofbiz-<revnumN>

...