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