You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by je...@comcast.net on 2004/06/02 22:13:13 UTC

Re: Jetspeed 2 build failure -- jars not found at ibiblio or bluesunrise

Things seem to be working somewhat better now, at least
related to the build.  I updated the sources yesterday and
was able to successfully compile the sources.  Deployment
following the four-step instructions at 

http://portals.apache.org/jetspeed-2/getting-started.html

seemed to succeed, but when I visited

http://localhost:8080/jetspeed

I received an error page indicating "/jetspeed is unavailable"
The log file under $CATALINA_HOME indicates that a number
of classes are not found (JetspeedContainerServlet, JetspeedException)
These should be found in the jetspeed-commons jar file, I believe.
Are there undocumented steps that must be followed?
This is a from-scratch build and install.  Tomcat 5 seems to be
working for all other deployed applications.

Any help is appreciated...

Cheers,
    Dan


> I think I understand what's happening.
> There are major refactorings going on in J2 since yesterday.
> One of which is the definition of a new subproject jetspeed-api.
> I haven't had the time to update my version to the latest cvs HEAD but I 
> guess there is already a jetspeed-api dependency defined but not yet 
> configured to be installed into the local maven repository.
> 
> Scott Weaver is leading these refactorings so maybe he can give some 
> feedback on the current state of cvs HEAD.
> 
> Scott, is the current HEAD buildable or should we wait until the 
> jetspeed-api refactoring is ready?
> Please give an indication then when we can expect it to be ready.
> 
> Regards,
> 
> Ate
> 
> OlsonE@lakeviewtech.com wrote:
> 
> > I am seeing the same problems Dan is when trying to run the instructions 
> > from http://portals.apache.org/jetspeed-2/getting-started.html - early in 
> > the build, I get the following warnings:
> > 
> > Attempting to download content-server-2.0-a1-dev.jar.
> > WARNING: Failed to download content-server-2.0-a1-dev.jar.
> > Attempting to download jetspeed-prefs-2.0-a1-dev.jar.
> > WARNING: Failed to download jetspeed-prefs-2.0-a1-dev.jar.
> > Attempting to download jetspeed-security-2.0-a1-dev.jar.
> > WARNING: Failed to download jetspeed-security-2.0-a1-dev.jar.
> > Attempting to download jetspeed-registry-2.0-a1-dev.jar.
> > WARNING: Failed to download jetspeed-registry-2.0-a1-dev.jar.
> > Attempting to download jetspeed-id-generator-2.0-a1-dev.jar.
> > WARNING: Failed to download jetspeed-id-generator-2.0-a1-dev.jar.
> > Attempting to download jetspeed-file-cache-2.0-a1-dev.jar.
> > WARNING: Failed to download jetspeed-file-cache-2.0-a1-dev.jar.
> > Attempting to download jetspeed-api-2.0-a1-dev.jar.
> > WARNING: Failed to download jetspeed-api-2.0-a1-dev.jar.
> > Attempting to download jetspeed-locator-2.0-a1-dev.jar.
> > WARNING: Failed to download jetspeed-locator-2.0-a1-dev.jar.
> > Attempting to download pluto-1.0.1-SNAPSHOT.jar.
> > 
> > Then the build continues to run a bit, then finally fails with this 
> > message:
> > 
> > +----------------------------------------
> > | Build and Install the Misc. Components jar Jetspeed-2 File Cache
> > | Memory: 34M/55M
> > +----------------------------------------
> > Attempting to download jetspeed-api-2.0-a1-dev.jar.
> > WARNING: Failed to download jetspeed-api-2.0-a1-dev.jar.
> > Attempting to download picocontainer-1.0-RC-1-SNAPSHOT.jar.
> > 
> > BUILD FAILED
> > File...... file:/C:/cvs-dev/jakarta-jetspeed-2/maven.xml
> > Element... maven:reactor
> > Line...... 93
> > Column.... 40
> > The build cannot continue because of the following unsatisfied dependency:
> > 
> > jetspeed-api-2.0-a1-dev.jar (no download url specified)
> > 
> > What am I missing?  I checked Ate's theory, but I only have a 
> > 'build.properties.sample' file in JS2 root (I haven't changed anything 
> > within JS2 root.)  I am getting the other jar dependencies, just not the 
> > ones listed above.
> > 
> > Thanks,
> > Eric Olson
> > 
> > 
> > 
> > 
> > Ate Douma <at...@douma.nu> 
> > 05/21/2004 04:24 AM
> > Please respond to
> > "Jetspeed Users List" <je...@jakarta.apache.org>
> > 
> > 
> > To
> > Jetspeed Users List <je...@jakarta.apache.org>
> > cc
> > 
> > Subject
> > Re: Jetspeed 2 build failure -- jars not found at ibiblio or bluesunrise
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Jetspeed wrote:
> > 
> > 
> >>Hello -
> >>
> >>I've just downloaded via cvsgrab the HEAD-tagged sources for Jetspeed 2.
> >>Maven is configured to use ibiblio and bluesunrise as remote 
> > 
> > repositories.
> > 
> >>It appears to be working, but when I attempt to run the indicated
> >>build command "maven allClean allBuild", I get a number of warnings 
> >>indicating
> >>that various jars have not been downloaded (some are), then the build
> >>fails with
> >>
> >>"Class Not Found: JDBC driver com.p6spy.engine.spy.P6SpyDriver could not 
> > 
> > 
> >>be loaded"
> > 
> > You must be using the sample build.properties provided in the J2 root. 
> > For initial building/testing you don't need it. It is an example 
> > configuration for using Oracle database (default hsqldb is used). If you 
> > do need Oracle (or MySql) please read:
> > http://portals.apache.org/jetspeed-2/database.html.
> > 
> > The p6spy driver is enabled by default in the build.properties.sample. 
> > For plain Oracle usage comment p6spy out (line 8) and remove the comment 
> >   on line 9.
> > 
> > 
> >>The missing jars are:
> >> content-server-2.0-a1-dev.jar
> >> jetspeed-api-2.0-a1-dev.jar
> >> jetspeed-file-cache-2.0-a1-dev.jar
> >> jetspeed-id-generator-2.0-a1-dev.jar
> >> jetspeed-locator-2.0-a1-dev.jar
> >> jetspeed-prefs-2.0-a1-dev.jar
> >> jetspeed-registry-2.0-a1-dev.jar
> >> jetspeed-security-2.0-a1-dev.jar
> >> struts-portlet-0.1.jar
> >> struts-portlet-spi-0.1.jar
> >>
> >>I cannot locate these on ibiblio/maven nor on bluesunrise/maven
> >>
> >>Any idea where these jars should be coming from?
> > 
> > Maven will try to resolve its dependencies with allClean also (but not 
> > fail). These jars are created when you do an allBuild. Because of your 
> > driver problems above allBuild failed. It should be resolved if you just 
> > remove build.properties or rename it back to build.properties.sample
> > 
> > Regards,
> > 
> > Ate
> > 
> > 
> >>Any help is greatly appreciated.
> >>
> >>Cheers,
> >>   Dan



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org