You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Ross Gardler (JIRA)" <ji...@apache.org> on 2009/08/31 22:45:32 UTC
[jira] Created: (WOOKIE-26) Standalone version of Wookie for
development
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
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.
Re: Standalone version of Wookie - ready to test
Posted by Ross Gardler <rg...@apache.org>.
2009/10/22 Ross Gardler <rg...@apache.org>:
> 2009/10/22 Ross Gardler <rg...@apache.org>:
>> 2009/10/22 Scott Wilson <sc...@gmail.com>:
>
>>> I've tested both approaches using JRun, and all the functional tests pass -
>>> the shindig integration doesn't work at this stage, but I'm pretty happy
>>> we've got it working for standalone Wookie without Shindig.
>
> Need to add the follwing to build.properties
>
> project.scripts.dir=scripts/derby
Nope, that was wrong. It fixed the problem I saw, but actually the
property that needs setting is either "project.using.derby" or
"project.using.mysql"
I suggest instead defining "wookie.database=[mysql|derby]" instead.
This will grewatly simply the builkd script by not having conditiuonal
target execution (although I appreciate some are comfortable with
functional programming may disagree).
Ross
Re: Standalone version of Wookie - ready to test
Posted by Ross Gardler <rg...@apache.org>.
2009/10/22 Scott Wilson <sc...@gmail.com>:
> That should work automatically - in build.xml:
See overlapping mail - it doesn't work automatically need to set one
of the "project.using.*" properties.
Ross
Re: Standalone version of Wookie - ready to test
Posted by Scott Wilson <sc...@gmail.com>.
That should work automatically - in build.xml:
<target name="set-mysql-script-dir" if="project.using.mysql">
<property name="project.scripts.dir" value="scripts/mysql"/>
</target>
<target name="set-derby-script-dir" if="project.using.derby">
<property name="project.scripts.dir" value="scripts/derby"/>
</target>
<target name="post-compile-core" depends="set-mysql-script-dir, set-
derby-script-dir">
<copy file="${project.scripts.dir}/widgetdb.sql" tofile="$
{project.build.classes.dir}/widgetdb.sql"/>
<copy file="${project.scripts.dir}/hibernate.cfg.xml" tofile="$
{project.build.classes.dir}/hibernate.cfg.xml"/>
</target>
On 22 Oct 2009, at 21:49, Ross Gardler wrote:
> 2009/10/22 Ross Gardler <rg...@apache.org>:
>> 2009/10/22 Scott Wilson <sc...@gmail.com>:
>
>>> I've tested both approaches using JRun, and all the functional
>>> tests pass -
>>> the shindig integration doesn't work at this stage, but I'm pretty
>>> happy
>>> we've got it working for standalone Wookie without Shindig.
>
> Need to add the follwing to build.properties
>
> project.scripts.dir=scripts/derby
>
> Ross
Re: Standalone version of Wookie - ready to test
Posted by Ross Gardler <rg...@apache.org>.
2009/10/22 Ross Gardler <rg...@apache.org>:
> 2009/10/22 Scott Wilson <sc...@gmail.com>:
>> I've tested both approaches using JRun, and all the functional tests pass -
>> the shindig integration doesn't work at this stage, but I'm pretty happy
>> we've got it working for standalone Wookie without Shindig.
Need to add the follwing to build.properties
project.scripts.dir=scripts/derby
Ross
Re: Standalone version of Wookie - ready to test
Posted by Ross Gardler <rg...@apache.org>.
2009/10/22 Scott Wilson <sc...@gmail.com>:
> OK guys, I think we're about ready to get some feedback on this from
> testers!
>
> I've done some more work on the build files, and it can now handle both:
>
> 1. Simple developer/testing startup using embedded jetty/derby
> 2. Build and deploy in production mode using tomcat/mysql
>
> I've updated the readme.txt with instructions for the second option.
Superb. Thanks Scott.
> I've tested both approaches using JRun, and all the functional tests pass -
> the shindig integration doesn't work at this stage, but I'm pretty happy
> we've got it working for standalone Wookie without Shindig.
can you tell us what test infrastructure you have in place. Perhaps
some bullet points on how to run the tests (I'll ANT script this for
you) when I return from my travels over the next couple of weeks)..
> If we get good feedback on this then I'm happy for the standalone branch to
> merge into trunk - and then lets see how quickly we can get to 0.8.1!
Don't we want to get Shindig running and tested first?
Ross
--
Ross Gardler
OSS Watch - supporting open source in education and research
http://www.oss-watch.ac.uk
Standalone version of Wookie - ready to test
Posted by Scott Wilson <sc...@gmail.com>.
OK guys, I think we're about ready to get some feedback on this from
testers!
I've done some more work on the build files, and it can now handle both:
1. Simple developer/testing startup using embedded jetty/derby
2. Build and deploy in production mode using tomcat/mysql
I've updated the readme.txt with instructions for the second option.
I've tested both approaches using JRun, and all the functional tests
pass - the shindig integration doesn't work at this stage, but I'm
pretty happy we've got it working for standalone Wookie without Shindig.
Its been hard going getting this process working but hopefully it'll
save us (and users) work in the future - thinks in particular to Ross
Gardler and Matthew Butler for their sterling efforts here.
If we get good feedback on this then I'm happy for the standalone
branch to merge into trunk - and then lets see how quickly we can get
to 0.8.1!
S
Re: [jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by Ross Gardler <rg...@apache.org>.
2009/10/22 Scott Wilson (JIRA) <ji...@apache.org>:
>
> [ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768648#action_12768648 ]
>
> Scott Wilson commented on WOOKIE-26:
> ------------------------------------
>
> Getting closer!
...
> - I've refactored the ivy.xml to retrieve "default" configurations for modules where possible. This means we don't get javadocs, sources, and dependencies used for building the dependencies (etc)
+1
> Some issues still with trying to use with Tomcat - I'll work on those next.
Thanks for your effort here. I assume since you are trying so hard you
feel this is a sensible route to take.
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.
>
>
--
Ross Gardler
OSS Watch - supporting open source in education and research
http://www.oss-watch.ac.uk
Re: [jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by Ross Gardler <rg...@apache.org>.
2009/10/21 Scott Wilson (JIRA) <ji...@apache.org>:
>
> [ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768260#action_12768260 ]
>
> Scott Wilson commented on WOOKIE-26:
> ------------------------------------
>
> I've applied the patches to the branch.
>
> Here are some issues I've identified when trying to build and run:
I don't understand any of the issues you identify as it is working
just fine on my build system, there should be no need to change
properties or config options.
> ====
> At this point I'm basically stuck. Rather than use an embedded Derby DB, the build is actually still pointing to MySQL in its hibernate.cfg.xml. And so the sql script won't run as the column order isn't the same in MySQL. (And I'm not sure I want it to be playing with my MySQL at this point anyway)
I can assure you it is not pointing at MySQL on my build machine. I am
checking out the branch now and will start from a clean machine.
> Happy to commit the fixes noted above if they make sense (being new to this whole Ivy thing)
Leave them out for now. Let me take a look at what it looks like on a
clean machine. This is a big patch and thigns can easily have got
messed up or missed out when I generated it.
I'll get back to you soon.
Ross
Re: [jira] Updated: (WOOKIE-26) Standalone version of Wookie for development
Posted by Ross Gardler <ro...@googlemail.com>.
On 15 Oct 2009, at 07:44, Hugh Barnard <hu...@googlemail.com>
wrote:
> Hi folks
>
> Thanks, when there's a complete patched one, I'll give it a spin and
> comment. May we have a few brief details for the system where the
> clean
> install currently worked?
The patch was originnaly built on OSX, Matthew was also on OSX. I
built it on a clean windows XP (Java 6) for my latest update. When we
have the code in SVN I'll rebuild it on a clean Linux machine.
You will also need Apache Ant (or working in an IDE that includes it,
such as Eclipse). Everything else will be brought in by the build
system. All you will need to do is 'ant run'
Ross
Sent from my mobile device.
>
> Incidentally, on a 'testing architecture' question, I decided it
> would be
> simpler to own the whole tool chain during experimentation (meaning,
> I can
> dip in anywhere), this makes this very attractive.
>
> Best regards Hugh
>
> On Wed, Oct 14, 2009 at 11:28 PM, Ross Gardler (JIRA)
> <ji...@apache.org>wrote:
>
>>
>> [
>> https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>>
>> Ross Gardler updated WOOKIE-26:
>> -------------------------------
>>
>> Attachment: updatedBuild.txt
>>
>> At the London meetup Matthew Bucket attempted to do an install on a
>> clean
>> machine using this patch. he had a few problems (and solved a
>> couple too).
>>
>> I've now created a working version on a completely clean machine,
>> this
>> needed a couple of changes, they are in this new patch. Note, this
>> needs to
>> be applied after the first patch as it only deals with changes
>> inthe build
>> system. There will, unfortunately, be some some conflicts, but they
>> will be
>> minor.
>>
>> Once we have the code in SVN (see INFRA-2273) I'll rebuild this
>> whole patch
>> against that. In the meantime people can apply these patches locally.
>>
>>> 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: 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.
>>
>>
>
>
> --
> http://www.hughbarnard.org
> http://www.big-wave-heuristics.com/
>
> http://www.hackney-environment-network.org.uk/
Re: [jira] Updated: (WOOKIE-26) Standalone version of Wookie for
development
Posted by Hugh Barnard <hu...@googlemail.com>.
Hi folks
Thanks, when there's a complete patched one, I'll give it a spin and
comment. May we have a few brief details for the system where the clean
install currently worked?
Incidentally, on a 'testing architecture' question, I decided it would be
simpler to own the whole tool chain during experimentation (meaning, I can
dip in anywhere), this makes this very attractive.
Best regards Hugh
On Wed, Oct 14, 2009 at 11:28 PM, Ross Gardler (JIRA) <ji...@apache.org>wrote:
>
> [
> https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Ross Gardler updated WOOKIE-26:
> -------------------------------
>
> Attachment: updatedBuild.txt
>
> At the London meetup Matthew Bucket attempted to do an install on a clean
> machine using this patch. he had a few problems (and solved a couple too).
>
> I've now created a working version on a completely clean machine, this
> needed a couple of changes, they are in this new patch. Note, this needs to
> be applied after the first patch as it only deals with changes inthe build
> system. There will, unfortunately, be some some conflicts, but they will be
> minor.
>
> Once we have the code in SVN (see INFRA-2273) I'll rebuild this whole patch
> against that. In the meantime people can apply these patches locally.
>
> > 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: 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.
>
>
--
http://www.hughbarnard.org
http://www.big-wave-heuristics.com/
http://www.hackney-environment-network.org.uk/
Re: [jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by Ross Gardler <rg...@apache.org>.
2009/10/22 Hugh Barnard <hu...@googlemail.com>:
> Hi Scott, Ross
>
> Since I'm following with a limited understanding of the internals and out
> the corner of my eye, please say on the list when you feel that you have a
> viable standalone. At that moment, I'll give it a spin, probably on XP. I
> actually only have XP and various flavours of Linux but not any kind/flavour
> of Mac,
Having you try it out now would be great. I have a viable standalone
version on my dev machine. Scott is finding some problems so clearly
there is still work to be done in getting SVN at a state where it will
run on anyones machine. Having you test it, even if you can't fix it,
would be great feedback for us.
We are working in branches/standalone if you want to give it a go.
There is a readme that should get you started - although it probably
needs further explanation. We are here (although I'm in the air for
most of the next three days).
Ross
>
> Best regards Hugh
>
> On Thu, Oct 22, 2009 at 10:32 AM, Scott Wilson (JIRA) <ji...@apache.org>wrote:
>
>>
>> [
>> https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768615#action_12768615]
>>
>> Scott Wilson commented on WOOKIE-26:
>> ------------------------------------
>>
>> Well, it can certainly build and run... but not quite correctly :( Jetty
>> isn't serving CSS correctly (wrong mime type) and there's something wrong
>> with the JS too. I'll investigate.
>>
>> I've also noticed that ivy is pulling in loads more jars than needed - I've
>> refactored it using "conf" attributes and got it working fine with far fewer
>> jars - I'll add that after checking out the other issues
>>
>>
>> (Shindig won't just work - it needs merging in its own dependencies plus
>> its own web.xml and a big pile of other files... best leave that to another
>> day.)
>>
>> > 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.
>>
>>
>
>
> --
> http://www.hughbarnard.org
> http://www.big-wave-heuristics.com/
>
> http://www.hackney-environment-network.org.uk/
>
--
Ross Gardler
OSS Watch - supporting open source in education and research
http://www.oss-watch.ac.uk
Re: [jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by Hugh Barnard <hu...@googlemail.com>.
Hi Scott, Ross
Since I'm following with a limited understanding of the internals and out
the corner of my eye, please say on the list when you feel that you have a
viable standalone. At that moment, I'll give it a spin, probably on XP. I
actually only have XP and various flavours of Linux but not any kind/flavour
of Mac,
Best regards Hugh
On Thu, Oct 22, 2009 at 10:32 AM, Scott Wilson (JIRA) <ji...@apache.org>wrote:
>
> [
> https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768615#action_12768615]
>
> Scott Wilson commented on WOOKIE-26:
> ------------------------------------
>
> Well, it can certainly build and run... but not quite correctly :( Jetty
> isn't serving CSS correctly (wrong mime type) and there's something wrong
> with the JS too. I'll investigate.
>
> I've also noticed that ivy is pulling in loads more jars than needed - I've
> refactored it using "conf" attributes and got it working fine with far fewer
> jars - I'll add that after checking out the other issues
>
>
> (Shindig won't just work - it needs merging in its own dependencies plus
> its own web.xml and a big pile of other files... best leave that to another
> day.)
>
> > 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.
>
>
--
http://www.hughbarnard.org
http://www.big-wave-heuristics.com/
http://www.hackney-environment-network.org.uk/
[jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768615#action_12768615 ]
Scott Wilson commented on WOOKIE-26:
------------------------------------
Well, it can certainly build and run... but not quite correctly :( Jetty isn't serving CSS correctly (wrong mime type) and there's something wrong with the JS too. I'll investigate.
I've also noticed that ivy is pulling in loads more jars than needed - I've refactored it using "conf" attributes and got it working fine with far fewer jars - I'll add that after checking out the other issues
(Shindig won't just work - it needs merging in its own dependencies plus its own web.xml and a big pile of other files... best leave that to another day.)
> 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.
[jira] Updated: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ross Gardler updated WOOKIE-26:
-------------------------------
Attachment: standalone-additions.tar.gz
standalone.diff
This patch does quite a few things, the summary is that it provides an almost zero configuration development environment.
The details are:
- use Apache Ivy for dependency management (thus we lose most of the jars from SVN)
- provide a start class that will start a development version of Wookie at http://localhost:8080
- provide an embedded Apache Derby database for use in development mode
- provide an embedded Jetty servlet container with pre-configured realms
- provide a simple means for starting the development server in debug mode (see readme.txt)
Since I am new to Wookie I cannot fully test everything so if someone more familiar can do some detailed testing I'd appreciate it.
> 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
> Assignee: Ross Gardler
> Attachments: standalone-additions.tar.gz, standalone.diff
>
> Original Estimate: 6h
> Remaining Estimate: 6h
>
> 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.
[jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Work logged: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_10895 ]
Ross Gardler logged work on WOOKIE-26:
--------------------------------------
Author: Ross Gardler
Created on: 31/Aug/09 03:22 PM
Start Date: 31/Aug/09 03:21 PM
Worklog Time Spent: 4h
Work Description: It work for me, but needs much more testing.
Issue Time Tracking
-------------------
Time Spent: 4h
Remaining Estimate: 2h (was: 6h)
> 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
> Assignee: Ross Gardler
> Attachments: standalone-additions.tar.gz, standalone.diff
>
> 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.
[jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768623#action_12768623 ]
Ross Gardler commented on WOOKIE-26:
------------------------------------
CSS is working fine for me. I do remember having to do a jetty config tweak to make it work (probably same for JS). Can't recall what it is, but it works on my clean machine.
Yes, the problem with automatic dependency resolution is that it pulls everything. I've excluded some jars already, but we have to be careful about excluding too many. They are only pulled down if one of the dependent jars says it is needed. If we actively exclude them from the build and later use a part of a library that needs that dependency we end up with a broken system. Since we can't predict what third parties are going to do with development of Wookie it is, in my opinion, safer to leave the dependencies in.
Ivy and Maven use the same repository, so each jar is only ever pulled down once.
Nice to know Shindig doesn't just work - we'll address that when Wookie works in this mode.
I suspect that you can see enough of what I'm trying to do here to make a decision as to whether you think this approach is the right one to take.
> 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.
[jira] Updated: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ross Gardler updated WOOKIE-26:
-------------------------------
Attachment: missingTweaks.diff
As my previous comment indicates, some items were missing from the original patches.
Here's a new patch (missingTweaks.diff) which is made against the SVN branch. Please revert your local changes as this patch fixes all the issues you identify in the way described in my earlier comment.
Note, I have not included commons-compress as you indicate you have already retreived this jar. It does need to go into ant/lib as it does not appear in a maven repository that I've found.
> 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.
[jira] Updated: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ross Gardler updated WOOKIE-26:
-------------------------------
Attachment: updatedBuild.txt
At the London meetup Matthew Bucket attempted to do an install on a clean machine using this patch. he had a few problems (and solved a couple too).
I've now created a working version on a completely clean machine, this needed a couple of changes, they are in this new patch. Note, this needs to be applied after the first patch as it only deals with changes inthe build system. There will, unfortunately, be some some conflicts, but they will be minor.
Once we have the code in SVN (see INFRA-2273) I'll rebuild this whole patch against that. In the meantime people can apply these patches locally.
> 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: 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.
[jira] Assigned: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ross Gardler reassigned WOOKIE-26:
----------------------------------
Assignee: (was: Ross Gardler)
Unassigning myself from this one. It needs review from a committer.
I've not run the tests against this, but I have done some manual tests.
> 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: standalone-additions.tar.gz, standalone.diff
>
> 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.
[jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768299#action_12768299 ]
Ross Gardler commented on WOOKIE-26:
------------------------------------
(working on a completely clean machine)
Seems I forgot to include the build.properties file in the patch. This configures the properties used in the build scripts. There is no need to change any build scripts just create a build.properties file in your project root with the following :
build.dir=build
ivy.repository.dir=ant
main.class.name=org.apache.wookie.server.Start
We shouldn't be hard coding values in the build scripts. This fixes:
Problem: Can't find ivysettings.xml
Problem: Can't resolve htmlcleaner, shindig
Problem: Class not found
Problem: Compile errors
Fix: Add commons-compress-1.0.jar to /ant/lib, and add to ivy.xml (as also noted above)
Yep, that seems to be missing from the patch too, also need to add the following to ivy.xml
<dependency org="commons-compress" name="commons-compress" rev="1.0">
</dependency>
----
Got to run for a bus now, will address the remaining issues when I get time (possibly tomorrow).
> 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: 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.
[jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768260#action_12768260 ]
Scott Wilson commented on WOOKIE-26:
------------------------------------
I've applied the patches to the branch.
Here are some issues I've identified when trying to build and run:
Problem: Can't find ivysettings.xml
Fix: Change ivy-common.xml to point to "ant/ivysettings.xml"
Problem: Can't resolve htmlcleaner, shindig
Fix: Change ivysettings.xml to point to "${basedir}/ant/lib/[artifact]-[revision].[type]"
Problem: Compile errors
Fix: Add commons-compress-1.0.jar to /ant/lib, and add to ivy.xml (as also noted above)
>From this point on we can build. Now onto running.
Problem: Class not found
Fix: Add <property name="main.class.name" value="org.apache.wookie.server.Start"/> to ivy-java-common.xml
Problem: Null pointer in Start.class
Fix: Move the "widgetdb_derby.sql" file into /src/ so the classloader can access it
====
At this point I'm basically stuck. Rather than use an embedded Derby DB, the build is actually still pointing to MySQL in its hibernate.cfg.xml. And so the sql script won't run as the column order isn't the same in MySQL. (And I'm not sure I want it to be playing with my MySQL at this point anyway)
Happy to commit the fixes noted above if they make sense (being new to this whole Ivy thing)
> 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: 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.
[jira] Updated: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ross Gardler updated WOOKIE-26:
-------------------------------
Fix Version/s: 0.8.1
> 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
> Assignee: Ross Gardler
> Fix For: 0.8.1
>
> Attachments: standalone-additions.tar.gz, standalone.diff
>
> 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.
[jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Matthew Buckett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765068#action_12765068 ]
Matthew Buckett commented on WOOKIE-26:
---------------------------------------
ant/build.xml doesn't seem to import the ivy stuff.
> 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: standalone-additions.tar.gz, standalone.diff
>
> 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.
[jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765703#action_12765703 ]
Ross Gardler commented on WOOKIE-26:
------------------------------------
ant/build.xml is the legacy build file. I've not touched it so as not to break the build whilst we iron out the problems here.
Standard practice is to put build.xml in the root of the project so I've added the ivy based build flie there. So we only need to do ant in the root.
> 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: standalone-additions.tar.gz, standalone.diff
>
> 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.
[jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768648#action_12768648 ]
Scott Wilson commented on WOOKIE-26:
------------------------------------
Getting closer!
- I've fixed the CSS/JS issue (it was a line in Mainfilter setting text/xml as default content type - Tomcat ignored it, Jetty didn't)
- I've fixed an issue with DWR (repos version is 2.0.3, we need 2.0.5 - I've added it to ant/lib)
- I've refactored the ivy.xml to retrieve "default" configurations for modules where possible. This means we don't get javadocs, sources, and dependencies used for building the dependencies (etc)
Some issues still with trying to use with Tomcat - I'll work on those next.
> 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.
[jira] Assigned: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ross Gardler reassigned WOOKIE-26:
----------------------------------
Assignee: Ross Gardler
> 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
> Assignee: Ross Gardler
> Original Estimate: 6h
> Remaining Estimate: 6h
>
> 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.
[jira] Commented: (WOOKIE-26) Standalone version of Wookie for
development
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754770#action_12754770 ]
Ross Gardler commented on WOOKIE-26:
------------------------------------
For this to work against the current CVS head at sourceforge we need to add:
<dependency org="commons-compress" name="commons-compress" rev="1.0">
</dependency>
To ivy.xml and place the commons-compress-1.0.jar in ant/lib (because the jar is not in any of the currently configured repositories)
> 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: standalone-additions.tar.gz, standalone.diff
>
> 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.