[ 
https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768493#action_12768493
 ] 

Ross Gardler commented on WOOKIE-26:
------------------------------------

I should point out that these patches only create a new build system. They do 
not prepopulate the database with the demo widgets and it does not do the 
Shindig stuff.

I didn't prepopulate with the widgets as I felt these should probably be split 
out from the default and deployed like any other widget. There is nothing 
stopping us putting the widget deployment data into the tables by adding 
relevant content to the SQL script of course.

As for Shindig, I'm hoping it will "just work" but without confirming the new 
build of Wookie works I didn't really see the point of testing Shinding.

Ross

> Standalone version of Wookie for development
> --------------------------------------------
>
>                 Key: WOOKIE-26
>                 URL: https://issues.apache.org/jira/browse/WOOKIE-26
>             Project: Wookie
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Ross Gardler
>             Fix For: 0.8.1
>
>         Attachments: missingTweaks.diff, standalone-additions.tar.gz, 
> standalone.diff, updatedBuild.txt
>
>   Original Estimate: 6h
>          Time Spent: 4h
>  Remaining Estimate: 2h
>
> A key objective for any open source project is to minimise the barriers to 
> entry for new developers. Currently a prospective developer needs to jump 
> through quite a number of hoops to get started (install tomcat, install 
> mysql, configure database, set up realms etc. etc.)
> On the mail list it was proposed and approved that we would create a version 
> that used Apache Derby (thus getting rid of the GPLd MySQL dependency) and 
> Jetty to provide a pre-configured development environment requiring zero 
> setup.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to