succeeding the mvn build the next step from the trunkREADME.txt is to run the webapp in jetty.
pointing my browser to localhost:8888 however I get: > HTTP ERROR: 503 > > SERVICE_UNAVAILABLE > > RequestURI=/ > > Powered by jetty:// and the console shows a stacktrace caused by NoClassFound on org/apache/avalon/excalibur/pool/TraceableResourceLimitingPool originating from the instantiation of some org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource after some digging I found - this missing class is provided by excalibur-pool-instrumented - which is a *provided* dependency from excalibur-datasources-2.2.1 (which is in turn required for our cocoon-databases-impl block) for now I've just added an explicit dependency from our databases-impl to this pool-instrumented which makes me able to run cocoon 2.2. trunk (hurray!) > Index: blocks/cocoon-databases/cocoon-databases-impl/pom.xml > =================================================================== > --- blocks/cocoon-databases/cocoon-databases-impl/pom.xml (revision > 529640) > +++ blocks/cocoon-databases/cocoon-databases-impl/pom.xml (working copy) > @@ -83,5 +83,10 @@ > <artifactId>excalibur-datasource</artifactId> > <version>2.2.1</version> > </dependency> > + <dependency> > + <groupId>org.apache.excalibur.components</groupId> > + <artifactId>excalibur-pool-instrumented</artifactId> > + <version>2.2.1</version> > + </dependency> > </dependencies> > </project> anyone with an opinion? (like should it rather be the database-samples expressing the dependency?) -marc=
