Personally I prefer to begin with a svn checkout either from the trunk or a branch. So you can stay updated. Then later when creating your own repo you can cut this link or use svn external (sensitive). Of course using a release branch is safer. Note that this stratey is easier for me, because I can directly commit in the OFBiz repo, YMMV.
There are other strategies https://cwiki.apache.org/confluence/display/OFBIZ/SVN+Tips+-+svn_load_dirs+Vendor+Branch that you may adapt to your needs You might also not bother, extract from a package and forget it... Jacques Justin Dagostino wrote: > Bummer. > > What is the preferred approach to deploying OFBiz? Is it tar/zip the > entire OFBiz folder structure, copy, and extract?? > > > On Tue, Oct 22, 2013 at 4:42 PM, Jacques Le Roux < > [email protected]> wrote: > >> It was a WIP by Adam Heath but was discontinued recently >> >> https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic#OFBizAttic-Debian >> >> Jacques >> >> Justin Dagostino wrote: >>> Hi, >>> >>> I'm exploring some production deployment options that don't involve >>> installing SVN, Ant, etc. on the production servers. Aside from TAR'ing up >>> the entire project, copying it over, and un-packaging, etc., perhaps >>> creating an installable OS package is a more elegant solution. >>> >>> I came across the "debian" folder in OFBiz. First, is this meant to >>> provide the building blocks for creating an OFBiz Debian package? If not, >>> can anyone provide some insight in accomplishing such a task? >>> >>> Any help would be greatly appreciated. Thank you. >>> >>> >>> Justin
