Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
0.7, 0.8
-
None
-
None
-
Low
Description
When we deploy a plugin or plugin docs (or even just the plugin descriptor) the first thing that happens is that we update the plugins section of the site from SVN.
This checkout is at present, held in the build directory.
I have two issue with this:
1) if there is a separate checkout of the site on the local machine this is duplicated content
2) if a ./build.sh clean is performed the checkout is lost and therefore must be done again - wasting bandwidth and time
So, what to do...
For 1) we can allow a local property file to override the settings for the relevant ant properties in plugins/build.xml:
deploy.plugins.svn-dir
deploy.docs.svn-dir
For 2) we can change the checkout location to $FORREST_HOME/work/...
This checkout is at present, held in the build directory.
I have two issue with this:
1) if there is a separate checkout of the site on the local machine this is duplicated content
2) if a ./build.sh clean is performed the checkout is lost and therefore must be done again - wasting bandwidth and time
So, what to do...
For 1) we can allow a local property file to override the settings for the relevant ant properties in plugins/build.xml:
deploy.plugins.svn-dir
deploy.docs.svn-dir
For 2) we can change the checkout location to $FORREST_HOME/work/...