There does not seem to much interest in this area. Perhaps as they get
closer to a release and more people like us start to try to use
Jetspeed2, it will get to the top of the list.
It seems to be the usual problem of open source.
The guys writing code like to write code. They are also too involved in
the process to understand what others need to be told.
A lot of the documentation is really the developers talking to each
other about the neat features and why they did it rather than how it is
used.
In a commercial project, you would get the developers together with
customers and do some testing of the installation and operating
procedures. Thet would sit side by side and walk through the docs step
by step making notes about what is clear and what is not. In open source
this is hard to do and never gets done. The "clients" never get into the
process except through the forums. The information from the forums never
gets back into the docs unless a developer sees the problem and solution
and takes the initiative to fix the docs or installation procedure.
On the other hand, there is a lot of Jetspeed documentation so I think
that the development group understands the importance of providing good
documentation - they just have trouble making it relevent or complete.
For instance, they assume that I am a Maven user who is going to read
the Maven files (and I know where they are and what they are called???)
if I have any questions so there is no need to explain certain things.
They provide information that is not useful but miss out on things like
describing what a step actually does - what files are put where during
the step.
I would like to know more about Maven but the Maven documentation is
even worse and takes way too much reading between the lines to figure
out. I just do not have the time to do this given the state of the
documentation and the time available.
I am a big fan of Eclipse and Ant. I know that Maven and Ant are
integrated into Eclipse. I recall finding a document about setting
Jetspeed up under Eclipse but it was wrong as well.
BTW The bug in M4 is known by the error that it produces
"PortletAggregator error".
I have done so many installations now that I do not know what files on
my disk are good and which ones are from unsuccessful attempts. I will
clean up and then redo the binary install of M3 to see what I get. Then
I would like to get the whole thing into Eclipse and figure out how to
build it and deploy it from there. Then I want to build a
"customization" directory and Ant procedure to integrate my customized
files into a new release without losing my application.
This seems like a pretty sensible way to work but there is no
documentation on how to do this.
Are you going to try to get it going in Eclipse?
Ron
Riddle wrote:
Thank you for the info. I have been trying (unsuccessfully) to build
for a very long time and thought it was only me.
M3 was the last time I saw it work.
Is there a chance of the docs, scripts and libaries will be
straightened out?
----- Original Message ----- From: "Ron Wheeler"
<[EMAIL PROTECTED]>
To: "Jetspeed Users List" <[email protected]>
Sent: Monday, October 03, 2005 2:42 PM
Subject: Re: new user and eclipse
The documentation for getting Jetspeed installed is not in a useful
state and does not work correctly.
The version numbers on the libraries that maven puts in the
repository do not match what Jetspeed needs in some cases and in
other cases the library is missing.
I was never able to get it working with Eclipse or even by following
the directions in the getting-started.html.
The M4 snapshot that you are told to download has errors in it that
prevent maven from building it correctly.
You will get to the point of deploying it but it will fail to deploy
(tomcat dumps a lot when Jetspeed is accessed - read the archives for
more details.
I finally got a working jetspeed by downloading a binary version of
M3. I downloaded the binary release from
http://apache.mirror.rafal.ca/portals/jetspeed-2/
This worked but now I have to figure out a) what do I have or not
have and b) how to get the whole mess into Eclipse in a state that I
can customize it and build something useful.
I have received some very useful advice about how to separate and
manage my customizations from the jetspeed distribution. (probably in
the archives). The person who gave me the advice has already written
the Ant tasks to manage his customization but did not post the Ant
Script.
He did however give a pretty clear description of how it worked.
Can't do this until I get the Jetspeed sources/libraries into Eclipse
with a working Maven build .
There needs to be more attention paid to the installation
instructions and some real thought put into how web designers and
system managers who are not java programmers can get this mess
installed. I would be very interested in working with other similarly
minded people who are trying to get a web application built with
Jetspeed using Eclipse the way it is supposed to work - not from the
DOS or LINUIX command line. Maven is integrated into Eclipse, we
should not be futzing around with maven commands.
This is not my top priority but it is something that I want to get
working this month.
Ron
Jacek Wiślicki wrote:
Wiadomosc od Davide Parisi z 2005-10-03 22:57 brzmiala:
thanks Jacek, i know this, and eclise read some library like dom4j,
commons-io ecc. but my eclipse don't find library like aopalliance,
castor...i need to download some library but i don't know how make
that...:)
I see...:) Add to your Maven's project.properties a list of remote
repositories, like this:
maven.repo.remote = http://www.bluesunrise.com/maven/,
http://www.ibiblio.org/maven/, http://dist.codehaus.org/,
http://cvs.apache.org/repository
If some download problems appear with Maven, you can download the
libraries manually (from any of the above locations) and place them
in your local repository as groupId/jars/artifactId-version.jar,
e.g. for a "sample" dependency in project.xml:
<dependency>
<groupId>group_name</groupId>
<artifactId>lib_name</artifactId>
<version>lib_version</version>
<type>jar</type>
</dependency>
use:
group_name/jars/lib_name-lib_version.jar
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
