[JIRA] Closed: (OFBIZ-775) Templating config files for version control

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Closed: (OFBIZ-775) Templating config files for version control

JIRA jira@ofbiz.org
     [ http://jira.undersunconsulting.com/browse/OFBIZ-775?page=all ]
     
Marco Risaliti closed OFBIZ-775:
--------------------------------

    Resolution: Won't Fix

Probably if no-one reply to this request it won't be fixed. If it not the case you can create a new issue.

> Templating config files for version control
> -------------------------------------------
>
>          Key: OFBIZ-775
>          URL: http://jira.undersunconsulting.com/browse/OFBIZ-775
>      Project: [OFBiz] Open For Business
>         Type: Improvement
>   Components: entity
>     Versions: SVN
>     Reporter: Chris Howe
>     Assignee: Jira Administrator
>     Priority: Minor

>
>
> As per this question on the subversion FAQ:
> --------------------------------------------------------------
> I have a file in my project that every developer must change, but I don't want those local mods to ever be committed. How can I make 'svn commit' ignore the file?
> The answer is: don't put that file under version control. Instead, put a template of the file under version control, something like "file.tmpl".
> Then, after the initial 'svn checkout', have your users (or your build system) do a normal OS copy of the template to the proper filename, and have users customize the copy. The file is unversioned, so it will never be committed. And if you wish, you can add the file to its parent directory's svn:ignore property, so it doesn't show up as '?' in the 'svn status' command.
> --------------------------------------------------------------
> Files like ${ofbizbase}/framework/entity/config/entityengine.xml
> 1)enitityengine.xml should be named entityengine.tmpl in svn
> 2)ofbiz should have an ant "prebuild" routine where
>   a)entityengine.tmpl gets copied in the build routine
>   b)user modifies local entityengine.xml to connect to proper database, etc or leaves built copy as is for default
> Unless there's another way to keep svn from building patches of potentially sensitive data (especially with the OSS financials app having account mappings in a properties files)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.undersunconsulting.com/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira