[Deploying Sakai] Maven hangs with "WAGON_VERSION: 1.0-beta-2"

[Adams, David]

It feels fragile to me to keep environment variables in the user login scripts, particularly if you need to run multiple Sakais or Java apps on the same server or if you try to keep a uniform user environment across multiple systems.

I've got a script that generates a full Sakai deployment that we use for setting up and maintaining production servers and test and dev instances. Part of that deployment are scripts that run Maven with the appropriate settings and a service control script for Sakai's Tomcat, each of which set the appropriate JAVA_OPTS, MAVEN_OPTS, CATALINA_OPTS, JAVA_HOME etc. We also make use of a common Maven setup to share a local Maven repository (on an NFS share) across multiple servers, rather than have to worry about 2+GB of Jar files filling up /home.

Note, this is all deployment stuff, not development setups, although it could work for development, too, particularly if you are juggling multiple instances for various purposes.

David Adams
Director of Learning Systems Integration and Support
Virginia Tech Learning Technologies



> -----Original Message-----
> From: production-bounces at collab.sakaiproject.org [mailto:production-
> bounces at collab.sakaiproject.org] On Behalf Of Paul Gibbs
> Sent: Friday, April 10, 2009 3:54 PM
> To: production at collab.sakaiproject.org
> Subject: Re: [Deploying Sakai] Maven hangs with "WAGON_VERSION: 1.0-
> beta-2"
> 
> Wow. I'm stunned--this is seriously the most helpful and responsive
> listserv I have ever joined. I received five responses within a matter
> of hours! Thank you!
> 
> I am going to try again with more RAM later today.
> 
> Where does everyone keep their environment variables? I created a
> standard user called sakai and gave the user rights on the tomcat
> directory, then created a variables.sh file in the user's home
> directory, sourced from .bashrc (I'm using Debian 5). Is that the
> normal way to do it?
> 
> Paul Gibbs
> Sent from my BlackBerry (267.261.4453)
> 
> -----Original Message-----
> From: Anthony Whyte <arwhyte at umich.edu>
> 
> Date: Fri, 10 Apr 2009 13:14:22
> To: <pgibbsjr at hotmail.com>
> Cc: <production at collab.sakaiproject.org>; <david.horwitz at uct.ac.za>
> Subject: Re: [Deploying Sakai] Maven hangs with "WAGON_VERSION: 1.0-
> beta-2"
> 
> 
> Paul--Sakai 2.5.4 tag and artifacts were built using Maven 2.0.8
>  (2.0.6+ is the recommended version).  So far as I am aware you are
>  the first to try and build it using Maven 2.1.0.  Can you back out
>  your Maven install and use instead Maven 2.0.10 or 2.0.8 available
>  from the archives.
> 
>  2.0.10
>  http://maven.apache.org/download.html
> <http://maven.apache.org/download.html>
> 
>  Archives
>  http://archive.apache.org/dist/maven/binaries/
> <http://archive.apache.org/dist/maven/binaries/>
> 
>  Cheers,
> 
>  Anthony
> 
>  On Apr 10, 2009, at 3:13 AM, Paul Gibbs wrote:
> 
>  > Hi all,
>  >
>  > I'm trying to install Sakai. I have installed JDK 1.5 update 18,
>  > Tomcat 5.5, Maven 2.1.0, and all successfully give me version
>  > listings. I have set my variables per the 2.5 install guide (http://
>  > confluence.sakaiproject.org/confluence/display/DOC/Install+Guide+-
>  > +Source+Install+%282.5%29) and downloaded sakai-2-5-4 through SVN.
>  > I went and successfully ran Maven on the sakai/master/pom.xml. When
>  > I back out to sakai/ and run Maven, it spits out a bunch of "[INFO]
>  > Somethingsomething" lines and then says
>  >
>  > WAGON_VERSION: 1.0-beta-2
>  >
>  > Nothing else happens after that. Although the CPU is chugging away,
>  > disk usage is close to nothing. Does anyone have any idea
>  > whatsoever as to what might be going on? Or at least perhaps point
>  > me in the right direction? (I don't even know what this means, much
>  > less how to troubleshoot it.) I'm hoping someone here can help
>  > me...I've been at this for days now. (!)
>  >
>  > Thank you!
>  >
>  > Paul Gibbs
>  >
>  >
>  >
>  >
>  > _______________________________________________
>  > production mailing list
>  > production at collab.sakaiproject.org
>  > http://collab.sakaiproject.org/mailman/listinfo/production
> <http://collab.sakaiproject.org/mailman/listinfo/production>
>  >
>  > TO UNSUBSCRIBE: send email to production-
>  > unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
> 
> TO UNSUBSCRIBE: send email to production-
> unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"