[ 
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.

Reply via email to