Author: crossley
Date: Wed Apr 25 20:46:08 2007
New Revision: 532596
URL: http://svn.apache.org/viewvc?view=rev&rev=532596
Log:
Explain where developers can get the sources for plugins.
Modified:
forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_90/usingPlugins.xml
Modified:
forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_90/usingPlugins.xml
URL:
http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_90/usingPlugins.xml?view=diff&rev=532596&r1=532595&r2=532596
==============================================================================
---
forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_90/usingPlugins.xml
(original)
+++
forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_90/usingPlugins.xml
Wed Apr 25 20:46:08 2007
@@ -206,6 +206,13 @@
<section id="local-deploy">
<title>Editing plugins sources to enhance functionality</title>
<note>
+ Of course, developers would need the sources. They are available via
+ <a href="site:build">SVN</a>. Alternatively, see your
+ $FORREST_HOME/build/plugins/ directory. Copy them somewhere for your
+ development and set the project.required.plugins.src property as
described
+ above. The SVN method is preferred.
+ </note>
+ <note>
Until issue
<a href="http://issues.apache.org/jira/browse/FOR-388";>FOR-388</a> is
fixed to enable the use of plugins in-place, any change to sources
