Lasso Soft Inc. > Home

  • Articles

Working with Subversion and LassoLab

This article provides a guide to working with subversion and LassoLab.

Subclipse (Subversion) for LassoLab

LassoLab can use Subclipse as a SVN client for Subversion — below is a quick setup guide for the process.

Installing Subclipse on OSX (Subversion):

  1. Check your svn version: svn --version
    • If it's not version 1.6.17 — then chances are you'll need to upgrade it, you can do so here:
    • http://www.collab.net/downloads/subversion (community versions). 
    • Registration is required — but this is the simplest route.
  2. Copy the relevant update site from here:
  3. In LassoLab click Help > Install New Software...
  4. Paste in the update site and click Add...
  5. Tick Subclipse then Next >
  6. Agree to terms then Finish
  7. Restart LassoLab
  8. If you get a JavaHL error, chances are you'll not running the the correct SVN version or didn't follow the SVN installation instructions. Try following this guide: http://www.dtumanov.com/post/3148267554/failed-to-load-javahl-library

Working with Subclipse and LassoLab

As Lasso projects require a specific folder structure, it's best not to checkout out your source directly to LassoLab as a project.

You can created a wrapper project folder to do so:

  1. Create a new folder in your repository called project, ie.
    • /repository/trunk/project
  2. Add a new svn:external property to the project folder:
    • webroot svn://svnserver/repository/trunk/src
    • Alternatively, you could branch your src as webroot.
  3. Import the repository into LassoLab, click:
    • File > Import > SVN > Checkout Projects from SVN > Next
  4. Either create or select your repository location ie.
    • svn://svnserver/repository
  5. Select your project folder, ie.
    • /repository/trunk/project
  6. Click next, and continue to setup as if it was a normal Lasso project.
  7. webroot will now be accessible and manageable by Subclipse

Working with New Projects.

With new projects it may make sense to store the entire project in SVN. This is a simple matter of creating a folder for your project in the repository and then creating a new project via: File > Import > SVN > Checkout Projects from SVN from there continue to click next and create the Lasso project. The entire project structure will be store within SVN.

Working With an External Subversion Client and LassoLab.

You don't need to use Subclipse with Lasso Lab, you can also use and external subversion client.

The simplest approach is to simply created a new Lasso project in LassoLab and then replace webroot with a checked out version of your project.

Alternatively you can use symbolic links or externals within LassoLab that point to local copys of your repositories.

Work With an External webroot:

  1. Create a new Lasso project
  2. Create project at existing location, ie. /Home/Projects/Example
  3. Click next — another dialogue will appear.
  4. Click "Link additional source"
  5. Select the webroot, ie. /Library/WebServer/Documents/Example
  6. Type webroot in the folder name
  7. Click finish

This will result in the webroot physically residing outside of the project — but crucially still be accessible to LassoLab for running and debugging purposes.

LassoLab is built on top of Eclipse one of the most configurable IDEs — if one of the above approaches does not work for you, then it's likely you'll be able to find one that does.

Author: Ke Carlton
Created: 15 Jun 2012
Last Modified: 15 Jun 2012

Comments

Scrum

by Olivi Jennifer, 21 May 2014

It will definitely ease your work of handling a big project. As a project manager I use scrum in my projects. One of my friends referred me to use the Guide to Scrum Body of Knowledge by http://www.scrumstudy.com. I like the concepts of sprints, daily standup meetings, etc. the SBOK Helped me alot in Understanding how <a href="http://www.scrumstudy.com/agile-project-management-training.asp">Agile Project Management</a> works.

Scrum in Project Management

by Olivi Jennifer, 21 May 2014

An agile process tends to focus on iterations, and client feedback, to allow for the inevitabilty of changing requirements whereas a waterfall process tries to define all requirements up front, and tends to be inflexible to changing requirements. You can learn more about agile and scrum by referring to some free resouces (http://www.scrumstudy.com/free-resources.asp) provided by scrumstudy or by attending any <a href="http://www.scrumstudy.com/">agile scrum certification</a> courses. I would personally suggest Agile Expert Certified course or <a href="http://www.scrumstudy.com/scrum-master-certification.asp">Scrum Master Certification</a> to you.

How to install and configure the EGit plugin for Eclipse (and LassoLab) to work with the Knop Project on GitHub

by Steve Piercy, 08 July 2012

I've posted written documentation and a video on a related topic, how to use git with Eclipse and LassoLab.

How to install and configure the EGit plugin for Eclipse (and LassoLab) to work with the Knop Project on GitHub
https://github.com/knop-project/knop/blob/master/docs/using_egit_with_the_knop_project.md

You must be logged in to comment.

Please note that periodically LassoSoft will go through the notes and may incorporate information from them into the documentation. Any submission here gives LassoSoft a non-exclusive license and will be made available in various formats to the Lasso community.

LassoSoft Inc. > Home

 

 

©LassoSoft Inc 2015 | Web Development by Treefrog Inc | PrivacyLegal terms and Shipping | Contact LassoSoft