Re: Build is broken

[Scott Wilson]

On 9 Mar 2010, at 22:12, Ross Gardler wrote:

On 07/03/2010 11:30, Scott Wilson wrote:

Wookie now won't run on my system either - I think the latest changes to

the build system have some problems.

If mine were the commits that broke this then I apologise and recommend you roll back those commits. I was in the middle of some work when my wife went into labour so may well have done something silly. I'm not able to look at what I did right now, so revert the commits and get your build working again (if you have not already done so).

No worries, I found it and fixed it. Oh oh, and it looks like I just broke the build now :-(

Ross

clean build without errors (calls to "default" configs changed to
"dev"). However "ant run" always then results in:

[java] Initial SessionFactory creation
failed.java.lang.ExceptionInInitializerError
[java] 11:06:56,085 ERROR log:? - failed

[java] java.lang.ExceptionInInitializerError
[java] at


[java] at


[java] at



[java] at


[java] at

[java] at

[java] at

[java] at

[java] at org.mortbay.jetty.Server.doStart(Server.java:210)
[java] at

[java] at org.apache.wookie.server.Start.startServer(Start.java:89)
[java] at org.apache.wookie.server.Start.main(Start.java:67)
[java] Caused by: java.lang.ExceptionInInitializerError
[java] at java.lang.Class.forName0(Native Method)
[java] at java.lang.Class.forName(Class.java:164)
[java] at


[java] at


[java] at


[java] at


[java] at

[java] at

[java] at


[java] at


[java] ... 12 more
[java] Caused by: java.lang.SecurityException: sealing violation:
package org.apache.derby.iapi.jdbc is sealed


same when trying to view /wookie in a browser

S

I fixed a couple of trivial errors that prevented "ant" to complete on a org.mortbay.jetty.webapp.webappcont...@21eabe{/wookie,build/webapp/ wookie} org .apache .wookie.util.hibernate.HibernateUtil.<clinit>(HibernateUtil.java:35) org .apache .wookie .server.ContextListener.contextInitialized(ContextListener.java:65) org .mortbay .jetty.handler.ContextHandler.startContext(ContextHandler.java:530) [java] at org.mortbay.jetty.servlet.Context.startContext(Context.java:135) org .mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java: 1218) org .mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java: 500) org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java: 448) org .mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) org .mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java: 117) org .mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) org .hibernate .connection .C3P0ConnectionProvider.configure(C3P0ConnectionProvider.java:114) org .hibernate .connection .ConnectionProviderFactory .newConnectionProvider(ConnectionProviderFactory.java:137) org .hibernate .connection .ConnectionProviderFactory .newConnectionProvider(ConnectionProviderFactory.java:79) org .hibernate .cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java: 448) org .hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:89) org.hibernate.cfg.Configuration.buildSettings(Configuration.java: 2101) org .hibernate.cfg.Configuration.buildSessionFactory(Configuration.java: 1325) org .apache .wookie.util.hibernate.HibernateUtil.<clinit>(HibernateUtil.java:31) Which would explain the "404" error Steve recently reported; I get the

smime.p7s
Description: S/MIME cryptographic signature