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 "McBride, Brian" <br...@hp.com> on 2006/02/10 09:42:18 UTC

Problems getting started, some severe

Hi Folks,

Trying to install Jetspeed 2 I encountered a few problems, which I
figured I'd pass on for your information.  Some of these are minor and
picky - but others are pretty disasterous.  The net is that the getting
started instructions do not work.

1.

 The out of the box binary installation does not run out of the box.
$/bin/catalina.bat relies on the environment variable _RUNJAVA being
set, which it is not on my machine.

2.

I wasted a lot of time because I installed and was trying to use the
current version of Maven.  To be fair, you do specify the version in [1]

[[
 Maven 1.0.2
]]

but this is easy to miss.  Drawing greater attention to it would be
helpful.   The limitation to Maven 1 is not mentioned on the plugin
documentation page [1], for example.

3.

On [1] it states:

[[
 The attribute values for username and password must correspond to the
specified values for
${org.apache.jetspeed.services.autodeployment.user}  and
${org.apache.jetspeed.services.autodeployment.user}  as described above.
]]

Presumably one of those
"${org.apache.jetspeed.services.autodeployment.user}" should be
"${org.apache.jetspeed.services.autodeployment.password}".

What it means by "as described above" is unclear.  I think this means
that the values should be the same as those specified in tomcat users
file.  I thought it meant there was an explanation of what variables are
and what those variables mean.  But there is no description like that
above.

4.

Section 4 of [1] talks about source and binary distributions.  The
section 5 talks about the binary distribution and the installer.  This
is a bit confusing.  Are we talking about building Jetspeed here, or
building a portal using Jetspeed.  And where does Maven come in?

I initially went for the installer, but then got confused when I tried
to create a new portal of my own.  That was yesterday.  I didn't
document that process so i'm not sure where I went wrong.  Looking at
the getting started with the install page [3] it tells you how to
install, then kinda drops you as a user of the portal.  A pointer to an
overview of how to create and configure your own portal would be very
helpful here.

[OK, I know this is open source, but I can't write it yet - I don't know
enough.  Documenting the problem I've encountered is the best I can do
at this stage.]

Section 4 of [1] would also be good place to put a paragraph about
options for the process of building a portal using Jetspeed, though that
is probably a link to a common page "getting started created your own
portal" page.

OK - I'm moving on to using the binary installation, reading [4]

5.  

Under section 3.1.2 of [4], this would be a good place to add a note
that if you get an error that maven cannot find plugin:download, or the
maven command is mvn not maven, then you are probably using maven 2
instead of the required maven 1.

6.

Running as per 3.2

[
maven j2:protal.genapp
]

I get the error message

[[

BUILD FAILED
File...... C:\Documents and
Settings\bwm\.maven\cache\maven-jetspeed2-plugin-2.0
\plugin.jelly
Element... fail
Line...... 635
Column.... 42
Required property org.apache.jetspeed.server.home undefined. See
http://portals.
apache.org/jetspeed-2/getting-started.html.
Total time: 15 seconds
Finished at: Thu Feb 09 08:48:43 GMT 2006 ]]

There is no reference to "org.apache.jetspeed.server.home" on [1]
However,  I think we can guess what it means.  Might be an idea to
include setting this property in 3.1.1 of [4].

Trying again, it also wants org.apache.jetspeed.catalina.version.major,
which is fairly obvious, and org.apache.jetspeed.server.shared -
presumably the name of the shared directory in Tomcat, and also
org.apache.jetspeed.deploy.war.dir (presumably the webapps directory).

Then it also wants org.apache.jetspeed.services.autodeployment.user and
org.apache.jetspeed.services.autodeployment.password.

This is getting suspicious.  Those really should have been defaulted.

And then it fails with 

[[
BUILD FAILED
File...... C:\Documents and
Settings\bwm\.maven\cache\maven-jetspeed2-plugin-2.0
\plugin.jelly
Element... fail
Line...... 698
Column.... 91
unsupported target database:
Total time: 6 seconds
Finished at: Thu Feb 09 09:06:49 GMT 2006

]]

Another missing defaulted property.  How many more and why - so lets try
cleaning out the installation so far and trying again.  Get same
problem.
ok.

But I find that some of these are documented later in section 3.4 of
this document.  So create the build.properties file in the project
directory and run again - and this time it seems to work.  Select hsql
as the database - not sure if that is right - buts supposed to be the
default.

Hmm, feeling a bit off track here, but it seems to have build something.



7.  

Next step is 3.5,  running

[[
maven war:install
]]

I get the following errors:

[[

Attempting to download portals-bridges-common-.jar.
Error retrieving artifact from [
http://www.ibiblio.org/maven/org.apache.portals
.bridges/jars/portals-bridges-common-.jar]: java.io.IOException:
Forbidden.
WARNING: Failed to download portals-bridges-common-.jar.
Attempting to download portals-bridges-velocity-.jar.
Error retrieving artifact from [
http://www.ibiblio.org/maven/org.apache.portals
.bridges/jars/portals-bridges-velocity-.jar]: java.io.IOException:
Forbidden.

...

Attempting to download derby-.jar.
Error retrieving artifact from [
http://www.ibiblio.org/maven/org.apache.derby/j
ars/derby-.jar]: java.io.IOException: Forbidden.
WARNING: Failed to download 

...

The build cannot continue because of the following unsatisfied
dependencies:

portals-bridges-common-.jar
portals-bridges-velocity-.jar
derby-.jar
]]

Hmm, looking at the website there is a portals-bridges-common-1.0.jar.
Maybe leaving the version # out is a way of asking for the latest in
Maven.  Or is this another dependency that is not working properly.  Yup
- a grep finds 

[[
bwm@mcbride-b-1 /c/Documents and Settings/bwm/.maven $ grep -r
portals-bridges-common- *
cache/maven-jetspeed2-plugin-2.0/plugin.jelly:    <copy
file="${maven.repo.local
}/${bridges.groupId}/jars/portals-bridges-common-${portals.bridges.commo
n.versio
n}.jar"
]]

So lets set the version numbers in the project properties file.  That
sorts out the Derby problem but the others remain.

It turns out that in ${base}/jetspeed-components.xml there is a
dependency on portals.bridges.version.  Define that to be "1.0" and the
build now succeeds.

8.

The next step is to start the database.  This initially fails, but
cleaning out the ${base} and starting again fixes that.

9.

The next step is to initialise the database using j2:quickStart.  I get
an error:

[[

BUILD FAILED
File...... C:\Documents and
Settings\bwm\.maven\cache\maven-jetspeed2-plugin-2.0
\plugin.jelly
Element... sql
Line...... 839
Column.... 44
Class Not Found: JDBC driver  could not be loaded Total time: 6 seconds
Finished at: Thu Feb 09 13:32:28 GMT 2006 ]]

Odd couple of lines in plugin.properties

[[
# You only need HSQL if you do not supply your own database
derby.include=true ]]

Are derby and hsql the same thing, or derby an evolution of hsql?  No -
apparently not - it came from Cloudscape.  So the damn thing doesn't
default to HSQL as advertised, seems to want to include derby whatever
one does.  There may be a transition in progres.  The binary version
uses HSQL.

The link in 3.6 on Database Configuration to  is broken.  Oh well. 

I find that [6] was written by someone with a sense of humour

[[
The default database distributed with Jetspeed-2 is the Hypersonic SQL
Java Database (HSQL). HSQL runs in its own process outside of
Jetspeed-2. It is not a production-ready database, however it allows you
to get up and running quickly. 
]]

but also 

[[
JDBC drivers are configured to work with the Maven build by adding your
specified JDBC driver jars to the Maven class path. Specify the jars
with the org.apache.jetspeed.test.jdbc.drivers.path  and
org.apache.jetspeed.production.jdbc.drivers.path  properties in your
$HOME/build.properties.
]]

So lets try that if we can find the right .jar file.  That doesn't cure
it.  I wish I know how to get maven to write out what it thinks its
trying to do.

I spot a link to some pdf documentation [7] at the head of [6], but
alas, that 404's.


Brian McBride  


[1] http://portals.apache.org/jetspeed-2/getting-started.html
[2] http://portals.apache.org/jetspeed-2/j2-maven-plugin.html
[3] http://portals.apache.org/jetspeed-2/getting-started-installer.html
[4] http://portals.apache.org/jetspeed-2/getting-started-binary.html
[5] http://portals.apache.org/jetspeed-2/guide-database.html
[6] http://portals.apache.org/jetspeed-2/guides/guide-database.html
[7] http://portals.apache.org/jetspeed-2/jetspeed2.pdf

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


Re: Problems getting started, some severe

Posted by Aaron Evans <aa...@yahoo.ca>.
McBride, Brian <brian.mcbride <at> hp.com> writes:

> 
> Hi Folks,
> 
> Trying to install Jetspeed 2 I encountered a few problems, which I
> figured I'd pass on for your information.  Some of these are minor and
> picky - but others are pretty disasterous.  The net is that the getting
> started instructions do not work.

Brian,
I had spotted some of these before and posted about it:

Unfortunately, I can't figure out how to get a URL to a thread in the
mail archives.

But this one should bring you to my post:

http://mail-archives.apache.org/mod_mbox/portals-jetspeed-user/200601.mbox/
%3cloom.20060125T194815-201 <at> post.gmane.org%3e

[J2 - 2.0] - Binary Build - Documentation and Build Process Issues
Posted Wed, 25 Jan 2006 19:52:56 GMT


As for the database, I use mysql.  You need only create the j2 database and give 
a user name and password and then specify the paths to your driver and you are
all set. That way, no messing around with derby and hssql.

I think originally, before the release of 2.0, hssql was the default DB and
then it got changed to derby, but not all the documentation has been updated
to reflect that.

HTH,
aaron 


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