[Building Sakai] Build source Sakai - Error ???

[Anthony Whyte]

Phuc--can you send us your catalina.out file so that we can look at  
the startup errors you are encountering.  Second, you can import the  
source artifact of Sakai after unpacking it into Eclipse.  As for the  
"base" issue, it sounds like you imported the Sakai source code as a  
Maven project as opposed to the default Eclipse project import (e.g.,  
file > import > Maven Projects vs file > import > "existing projects  
into workspace").  I regularly import Sakai into Eclipse as a set of  
Maven projects since the maven import option allows me to work more  
easily with the Maven pom.xml files (particularly each "base" pom)  
that describe each Sakai module, so it's not necessarily a wrong choice.

What you are seeing (at least I hope you are seeing) is Sakai  
organized as a set of Maven projects, the "base" folder representing  
as well as holding the "base" pom.xml file.  If you expand the tree  
view of the base folder you should see the entire set of Sakai  
projects that reference the "base" pom as thier parent pom:

base
	access
	alias
	announcement
	. . .  etc. [remaining Sakai projects]

If you were to expand /access, for instance, you will see its "base"  
pom.xml (a child of the root "base" pom.xml) file which references  
the set of sibling access modules:

<modules>
     <module>access-impl/impl</module>
     <module>access-tool/tool</module>
     <module>web-tool</module>
   </modules>

Sakai complicates the Maven picture a bit by describing project-wide  
or general Maven properties, dependencies, repositories, reporting  
plugins and build directives in the the /master project's pom.xml  
file.  Hopefully, you can see all this as you traverse the folders in  
Eclipse.

However, if you want to dispense with this Maven "view" and import  
Sakai as a set of "Eclipse projects"  you can simply delete the  
Eclipse metadata .project and .classpath files located currently in  
your root Sakai source folder and created when you first imported the  
projects into Eclipse.  Doing so clears out the reference to your  
project being an Eclipse Maven project.   Then reimport the project  
(e.g., file > import > "existing projects into workspace").

Also, it's good practice to regenerate the Eclipse metadata files  
(e.g., .classpath) before importing Sakai into Eclipse in order to  
ensure that the path references contained therein are up-to-date.  To  
do so, simply issue the following Maven commands from your Sakai  
source folder:

mvn eclipse:clean
mvn eclipase:eclipse

Cheers,

Anthony


On Mar 17, 2009, at 2:19 AM, de men wrote:

> Dear,
> I finally built it successfully.
> But after I deployed to tomcat, I could not start Sakai with  
> startup.bat ???
> Another question is:
> According to guides on Sakai pages about developing Sakai in  
> Eclipse. They used the source code downloaded by SVN.
> Why can not I use the source release on Sakai page ??? When I  
> imported it to Eclipse, there was only a project named "base" ???
>
> Looking forward to your answers.
> Thanks.
>
> Phuc Bui
> -------------------------
> Search occasionally throws test errors during startup; in this case, a
> REST-style HTTP Post request failed. If you simply want to start  
> Sakai you can
> prevent Maven from throwing build errors when the Surefire test plugin
> encounters a test failure by adding the parameter - 
> Dmaven.test.skip=true to your
> set of mvn goals when running maven from the command line:
>
> mvn clean install -Dmaven.test.skip=true sakai:deploy
>
> If you want more info on the error add the "-e" switch:
>
> mvn -e clean install sakai:deploy
>
> Cheers,
>
> Anthony
>
> Bạn luôn muốn kết nối với nhiều bạn bè hơn trên  
> blog và trang web cá nhân?
> Tạo Pingbox mới nhất ngay hôm nay!