On 12/10/01 9:57 AM, "John Wooten" <[EMAIL PROTECTED]> wrote:

> Why does this keep getting released with a set of instructions that say,
> drop the jetspeed war file into the tomcat webapps and then start the server
> and it will work?
> 
> Once again, I did that.
> I then connected to Jetspeed via the browser, logged in as turbine, turbine.
> Got logged in.  Then chose Customize and got the same page as after logging
> in.  NO CUSTOMIZATION.
> 
>
> 
> --------PLEASE NOTE.  This was reported as a problem over a week ago.  NO
> ANSWER AS TO HOW TO FIX, WHERE TO LOOK, OR A WORK AROUND.  NEW RELEASE STILL
> DOES EXACTLY THE SAME THING AS BEFORE>

Also note that you have the source as every other __volunteer__ who works on
the jetspeed project. Maybe you might actually consider lending a hand in
helping to find a solution instead of complaining in BOLD. David, Raphael,
Paul, Nacho and the rest of Jetspeed developers all volunteer their time to
help you and everyone else who uses Jetspeed. The releases may not be as
frequent or as well documented as you would like, but it is in your power to
fix this by helping.
 
> OBVIOUSLY THERE IS A SETUP PROBLEM.  WHAT ELSE IS NECESSARY TO GET THIS TO
> WORK?  IS THERE A PIECE OF INFORMATION MISSING?  DOES SOMETHING ELSE NEED TO
> BE INSTALLED OTHER THAN JUST DROP THE WARFILE INTO THE WEBAPPS AND IT WILL
> WORK?

Maybe there is a disconnect between the users and developers but you as a
user who cannot get this to work are in an ideal situation to find out what
the problem is and document a solution. As often is the case the core
developers have setups that are tried and tested and can sometimes miss
things that are not at all obvious to inexperienced users. You can fix the
problem once and for all with a  little digging, documenting and testing. If
you're not will to fix it why do you expect anyone else to? The core
developers of Jetspeed do what they can and need help when problems like
this arise.
 
> Inquiring minds really would like to join the in-crowd and get their setup
> so it will work like everyone else who apparently can run these releases.

Like I said it's in your power to fix the problem. Just because you report
the problem doesn't mean a solution is imminent. And it's not likely that
too many developers are going to go out of their way to help someone who
sends a somewhat accusatory messages to the list, even if borne out of
frustration. Trust me it won't get you very far and it certainly won't help
you garner any help from the people who actually work on the project.
 
> 
> 
> -----Original Message-----
> From: David Sean Taylor [mailto:[EMAIL PROTECTED]]
> Sent: Monday, December 10, 2001 1:41 AM
> To: 'Jetspeed Users List'
> Subject: Jetspeed release 1.3a2 candidate
> 
> 
> There is a 1.3a2 release candidate at
> 
> http://jakarta.apache.org/builds/jakarta-jetspeed/release/v1.3a2/
> 
> If you get a chance, please give it a try and let us know how it works for
> you.
> 
> The documentation is updated at http://jakarta.apache.org/jetspeed
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 
> 
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>

-- 

jvz.

Jason van Zyl

http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to