You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Matthew Buckett (JIRA)" <ji...@apache.org> on 2010/02/12 10:48:28 UTC
[jira] Created: (WOOKIE-117) Allow hot deploy from directory
Allow hot deploy from directory
-------------------------------
Key: WOOKIE-117
URL: https://issues.apache.org/jira/browse/WOOKIE-117
Project: Wookie
Issue Type: New Feature
Components: Server
Reporter: Matthew Buckett
It would make widget development faster if rather than having to re-deploy the widget (with ant) every time you changed a file wookie would just monitor the whole uncompressed folder for changes.
This is similar to how Tomcat works when you edit a expanded WAR.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WOOKIE-117) Allow hot deploy from directory
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Wilson updated WOOKIE-117:
--------------------------------
Fix Version/s: 0.8.2
We should definitely look at this for a future release - a simplified edit and deployment lifecycle would be great and this is a nice start.
> Allow hot deploy from directory
> -------------------------------
>
> Key: WOOKIE-117
> URL: https://issues.apache.org/jira/browse/WOOKIE-117
> Project: Wookie
> Issue Type: New Feature
> Components: Server
> Reporter: Matthew Buckett
> Fix For: 0.8.2
>
> Attachments: WOOKIE-117.patch
>
>
> It would make widget development faster if rather than having to re-deploy the widget (with ant) every time you changed a file wookie would just monitor the whole uncompressed folder for changes.
> This is similar to how Tomcat works when you edit a expanded WAR.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WOOKIE-117) Allow hot deploy from directory
Posted by "Matthew Buckett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew Buckett updated WOOKIE-117:
-----------------------------------
Attachment: WOOKIE-117.patch
Small patch to Wookie from the day at Oxford.
This allows deployment from an unpacked folder in the widgets hot deploy folder.
After deployment it doesn't delete the folder so the user can edit it and continues to scan it for changes and reloads any changes.
It could do with a little refactoring (remove recursion? move out ZIP code).
Ideally they way Widgets are loaded into the system should be looked at but this patch adds the feature with the minimum of changes.
> Allow hot deploy from directory
> -------------------------------
>
> Key: WOOKIE-117
> URL: https://issues.apache.org/jira/browse/WOOKIE-117
> Project: Wookie
> Issue Type: New Feature
> Components: Server
> Reporter: Matthew Buckett
> Attachments: WOOKIE-117.patch
>
>
> It would make widget development faster if rather than having to re-deploy the widget (with ant) every time you changed a file wookie would just monitor the whole uncompressed folder for changes.
> This is similar to how Tomcat works when you edit a expanded WAR.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.