[Building Sakai] Getting Sakai 10.1 into Eclipse environment

[Ryan VanDyke]

Both myself and a co-worker have also had these same issues following the walkthrough which does have you importing the entire Sakai source instance and not just individual tools so in theory it should work. The first error I get when following this guide happens right after attempting to import with a popup window:

==========================
Subversion Native Library Not Available
Errors: Incocmpatible JavaHL library loaded. 1.6.x or later required.
==========================

However in "Eclipse Installation Details" it shows under "Features" that JavaHL 1.6.17 is installed from tigris.org along with the Subclipse JavaHL Native Library Adapter. All versions also match as outlined here:

http://subclipse.tigris.org/wiki/JavaHL#head-1c75c22d4d8e9c3cd16868bdd3d6157637589ef0

Switching the client to SVNKit (Pure Java) got me at least a little farther in downloading resources but doing this was not mentioned in the guide.

I'm on Windows 7 using Luna Release: Eclipse 4.4.0. Guide says to use 3.3+ so should I try downgrading eclipse?

One thing it mentions is adding the M2_REPO classpath variable in Eclipse with the path to the local maven repository. Mine already existed in the install and said it could not be modified. I made sure to move the repo to that path just in case but no luck.

- Ryan


From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Matthew Jones
Sent: Thursday, September 25, 2014 9:34 AM
To: ahmed adel
Cc: Developers Sakai-Dev
Subject: Re: [Building Sakai] Getting Sakai 10.1 into Eclipse environment

Nope, those instructions still work for me. Using Eclipse 3.8.1 on Ubuntu with really just the Java Development Tools.  Typically I just import a the specific tool I'm working with rather than the entire source. I've never tried to get Eclipse to build the entire project from the top level, and not sure if it can. So I kind of do a mix of command line and Eclipse. Do the code editing and debugging in eclipse, and the mvn commands and deployment on the command line.

So if you want to import gradebook (and maybe kernel) you run 

mvn clean install (Build the entire project first)

Then go into the tool(s) you want in eclipse and run
mvn eclipse:clean
mvn eclipse:eclipse 

and import those in eclipse (8)

And as long as you do step 5 and set your M2_REPO to the repository location it works for me. I mostly use Eclipse for remote debugging and working on bugs/features for one tool at a time. 

On Thu, Sep 25, 2014 at 8:58 AM, ahmed adel <abou.alseoud at gmail.com> wrote:
Dear all,

I faced some trouble in my way of importing Sakai source into my Eclipse dev. environment following the tutorial "Importing Sakai source into Eclipse" https://confluence.sakaiproject.org/display/BOOT/Import+Sakai+source+into+Eclipse

I followed the steps and after importing the project, maven nature wasn't recognized and 75000+ errors appeared. After that, i tried to import Sakai as maven project and 2000+ errors also appeared. 

Anyone have another tutorial to import Sakai 10.1 into Eclipse or anyone faced the same problems??

_______________________________________________
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"


 --------------------------------------------------------------------------------------------------------------------

***NOTICE*** This e-mail and/or the attached documents may contain technical data within the definition of the International Traffic in Arms Regulations and/or Export Administration Regulations, and are subject to the export control laws of the U.S. Government. Transfer of this data by any means to a foreign person, whether in the United States or abroad, without an export license or other approval from the U.S. Department of State or Commerce, as applicable, is prohibited. No portion of this e-mail or its attachment(s) may be reproduced without written consent of Kratos Defense & Security Solutions, Inc. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient or believe that you may have received this document in error, please notify the sender and delete this e-mail and any attachments immediately.