Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Required Software

...

  • 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.

...

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:

Code Block
mvn eclipse:eclipse

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

 For information about fixing the build errors, check out Developer Bootstrap on fixing eclipse build issues.