[Building Sakai] Sakai 10.2 deployment

Sam Ottenhoff ottenhoff at longsight.com
Fri Oct 17 06:12:14 PDT 2014


Did you follow the install instructions?
https://confluence.sakaiproject.org/pages/viewpage.action?pageId=93028745


7.0 Build, deploy and start up Sakai in Tomcat

Install the Sakai master project

Sakai makes use of Maven's Project Object Model to provide an XML
representation of basic project information covering dependency management,
build targets, external repositories, issue tracking, mailing lists,
reporting plugins, developer bios, etc. A top-level master pom.xml file
located in the /master project acts as a parent for other Sakai pom.xml
files. If you are building Sakai for the first time you should install the
master project first by issuing the clean andinstall goals from the
/master project
folder.

cd master
mvn clean install
cd ..

Install and deploy Sakai

Once you have built the master pom, issue the following Maven goals from
the top-level Sakai source directory:

[image: (info)] -Dmaven.tomcat.home specifies Tomcat's
location. -Dsakai.home specifies the location of the sakai properties
file(s) within Tomcat. -Djava.net.preferIPv4Stack can help resolve issues
with Maven hanging while attempting to pull from certain
repositories. These can be omitted if specified in Maven's settings.xml file
(version 2.x) or in MAVEN_OPTS (version 3.x).

mvn clean install sakai:deploy -Dmaven.tomcat.home=/pathto/tomcathome
-Dsakai.home=/pathto/tomcathome/sakai -Djava.net.preferIPv4Stack=true

Your first Sakai build will take some time as Maven downloads and stocks
your local .m2/repository with missing dependencies while performing the
build and deploying *.war** and *.jar files to Tomcat's
$CATALINA_HOME/webapps, $CATALINA_HOME/components and
$CATALINA_HOME/shared/lib folders. If during this process Maven reports
that the build failed read the accompanying error message carefully to
troubleshoot the issue (see the Troubleshooting
<https://confluence.sakaiproject.org/pages/viewpage.action?pageId=93028745#>
 section).

You can also issue mvn clean install sakai:deploy from any sakai project
module top-level folder in order to build and deploy portions of Sakai such
as individual tools.

On Fri, Oct 17, 2014 at 8:59 AM, Igor Novopashenny <
igor at escience.uni-bremen.de> wrote:

> Hello!
>
> I tied to deploy the sakai10.2
>
> And get an error
>
> [ERROR] The build could not read 1 project -> [Help 1]
>
> [ERROR]
>
> [ERROR]   The project org.sakaiproject:base:10-SNAPSHOT
> (/opt/sakai-src/sakai-10.2/pom.xml) has 1 error
>
> [ERROR]     Non-resolvable parent POM: Could not find artifact
> org.sakaiproject:master:pom:10-SNAPSHOT and 'parent.relativePath' points at
> wrong local POM @ line 5, column 13 -> [Help 2]
>
>
>
> Can you help?
>
> Regards Igor
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20141017/304078d6/attachment.html 


More information about the sakai-dev mailing list