Skip to end of banner
Go to start of banner

Bootstrap on Ubuntu Linux

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Required Software

  • Java 1.6+
  • Maven 3.0.3+
  • Git (not ancient...)
  • Eclipse for Java EE developers (I used 3.7 Juno)

For ubuntu the first three are easy.  Well, Sun Java can be a bit tricky in the newer versions, but there are already plenty of guides about how to do that on the internet.

Eclipse is also easy, just download and unzip.

Setting up Eclipse

You need to add some software sources for the Eclipse plugins:

Go to the Preferences page then Install/Update->Available Software

Add these url's one by one as new software sources (using the add button to the left)

  • m2e  url: http://download.eclipse.org/technology/m2e/releases
  • gwt   url: http://dl.google.com/eclipse/plugin/3.7
  • (optionally) egit url: http://download.eclipse.org/releases/juno
    • note that I don't use the eclipse git integration so I can't speak to it's stability, usability etc.

Close the preferences pane.  Now go to Help -> Install New Software

First(for no particular reason) install GWT plugins :

Type gwt into the Work with box.

When the info loads, select the Google Plugin for Eclipse and the SDK -> Google Web Toolkit SDK 2.4.0.  Selecting the SDK as well means you don't have to separately install GWT.  Continue through the dialogs, accept the license agreements and eventually finish.  Let Eclipse install everything and restart.  Say ok if it asks you about unsigned content (we trust Google, right?)

Now go back to the Install New Software Dialog and this time work with the m2e source.

Here I selected only the m2e plugin itself, and not the optional logging component.

Again, wade through the dialogs and eventually finish and let eclipse install restart.

Maven Build

Now follow the instructions for Getting the Maven Build Working in the Developer Bootstrap page.

Importing Projects

Now you should be ready to start importing your projects.  Before you do this section you should follow the instructions on forking and cloning the code repo's

Go to File -> Import -> Maven -> Existing Maven Projects

Now hopefully, you did the smart thing and put all the sage projects in one common root folder.  If so, browse to that location in the Root Directory box.  Maven will recursively scan the directories and find all maven projects.  You are then presented with a list.  Choose the projects that are actually sage related (Portal, Repostiory-Services), also including all the sub-projects under Repo and click next.  Accept eclipse's automatic mapping of maven plugins to eclipse plugins.  Ignore it if can't find a match for javacc, we'll fix that in a moment.  Eclipse will probably complain that if you continue you will have projects with build errors.  Accept and bravely continue on.  Keep accepting, and continuing until Eclipe finishes installing and restarting.

At this point, I closed Eclipse again (actually, it crashed) and ran:

mvn eclipse:eclipse

in the root of portal and repo-service directories.  This generates eclipse files using maven's version of the classpath.

 

  • No labels