You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Ross Gardler (JIRA)" <ji...@apache.org> on 2005/06/16 02:52:48 UTC
[jira] Created: (FOR-544) Update plugin docs deployment
Update plugin docs deployment
-----------------------------
Key: FOR-544
URL: http://issues.apache.org/jira/browse/FOR-544
Project: Forrest
Type: Task
Components: Plugins (general issues)
Versions: 0.7-dev
Reporter: Ross Gardler
Priority: Blocker
Fix For: 0.7-dev
As discussed on list we need to change the way the plugin docs are deployed for the 0.7 release.
I've now implemented the necessary changes. The final solution is slightly different to that which was posted to the list in order to simplify its implementation within the existing build system.
The change from that discussed on list is that instead of deployiong to http://f.a.o/plugins_0_70 they are deployed to http://f.a.o/pluginDocs/plugins_0_70
Since we are in a code freeze we need committers to verify that this patch is OK to apply. Please cast your eye over the patch attached and cast you vote in the email thread I will start shortly after this issue is created.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (FOR-544) Update plugin docs deployment
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-544?page=all ]
Ross Gardler updated FOR-544:
-----------------------------
Attachment: pluginDocs.patch
> Update plugin docs deployment
> -----------------------------
>
> Key: FOR-544
> URL: http://issues.apache.org/jira/browse/FOR-544
> Project: Forrest
> Type: Task
> Components: Plugins (general issues)
> Versions: 0.7-dev
> Reporter: Ross Gardler
> Priority: Blocker
> Fix For: 0.7-dev
> Attachments: pluginDocs.patch
>
> As discussed on list we need to change the way the plugin docs are deployed for the 0.7 release.
> I've now implemented the necessary changes. The final solution is slightly different to that which was posted to the list in order to simplify its implementation within the existing build system.
> The change from that discussed on list is that instead of deployiong to http://f.a.o/plugins_0_70 they are deployed to http://f.a.o/pluginDocs/plugins_0_70
> Since we are in a code freeze we need committers to verify that this patch is OK to apply. Please cast your eye over the patch attached and cast you vote in the email thread I will start shortly after this issue is created.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (FOR-544) Update plugin docs deployment
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-544?page=all ]
Ross Gardler closed FOR-544:
----------------------------
Resolution: Fixed
Assign To: Ross Gardler
> Update plugin docs deployment
> -----------------------------
>
> Key: FOR-544
> URL: http://issues.apache.org/jira/browse/FOR-544
> Project: Forrest
> Type: Task
> Components: Plugins (general issues)
> Versions: 0.7-dev
> Reporter: Ross Gardler
> Assignee: Ross Gardler
> Priority: Blocker
> Fix For: 0.7-dev
> Attachments: pluginDocs.patch
>
> As discussed on list we need to change the way the plugin docs are deployed for the 0.7 release.
> I've now implemented the necessary changes. The final solution is slightly different to that which was posted to the list in order to simplify its implementation within the existing build system.
> The change from that discussed on list is that instead of deployiong to http://f.a.o/plugins_0_70 they are deployed to http://f.a.o/pluginDocs/plugins_0_70
> Since we are in a code freeze we need committers to verify that this patch is OK to apply. Please cast your eye over the patch attached and cast you vote in the email thread I will start shortly after this issue is created.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira