Argeo IDE

From ArgeoWiki

Jump to: navigation, search

The Argeo IDEs for various technologies are based on Eclipse. Eclipse is a great open source products, with a lively community and many extensions. However it is not the most stable and mixing plenty of plugins or using too early versions of new Eclipse release can lead to inconsistencies and a lot of headaches.

The ONLY supported configurations are the ones described below, configured in this order, with no more and no less plugins.

Note: if you are familiar with Eclipse, you can of course use whatever version and install whatever plugins you want. Take advantage of Eclipse workspaces, backing them up or duplicating them (simple directory copies), if you want to switch between the supported configuration and some more experimental ones. Just be aware that workspaces can be rendered inconsistent, so back your important ones before testing unsupported configurations on them.

Contents

Java

  • Requirement: command line Subversion and Maven have to be installed before setting up the IDE
  • Download Eclipse Galileo SR2 for RCP Development (Eclipse 3.5.2)
  • Install Eclipse by untaring/unzipping the downloaded archives
    • Tip: we recommend that you rename the 'eclipse' directory in 'eclipse-rcp-galileo-SR2', this will simplify future updates or installation of IDEs for other kind of development
  • Add all "required" features of the Subclipse plugin version 1.6
  • Add the only feature proposed for Maven Integration
    • update site: http://m2eclipse.sonatype.org/sites/m2e
    • Don't worry about the features not being signed, restart Eclipse as suggested by the installer
    • Add ONLY the feature "Maven Integration > Maven Integration for Eclipse (Required)" of the M2Eclipse plugin (again, ONLY this feature, which will imply a second one as a dependency). update site: http://m2eclipse.sonatype.org/update/
  • Install ONLY all the features of the categories "Core / Spring IDE" and "Extensions / Spring IDE"
  • Setup the Maven plugin
    • Go to "Windows > Preferences... > Maven", then check "Download Artifact Sources"
    • Go to "Windows > Preferences... > Maven > Installations", then using the "Add.." button, add your local Maven installation and check it as "Default"
    • Tip: Since the M2Eclipse plugin unfortunately references the name of the Maven installation directory in its launch configurations, you should do the following in order to simplify future upgrades of Maven:
      • on Linux, create a symbolic link 'apache-maven' to your particular Maven version, e.g. 'apache-maven-2.2.1', and point to the symbolic link
      • on Windows, rename your Maven directory to 'apache-maven' and point to the renamed directory
  • Make sure that you have checked out the whole project source tree using the command line subversion
  • Make sure that 'mvn clean install' from the command lien works on the whole checked out tree
  • ONLY THEN import projects in Eclipse, using "Right-Click in the Package Explorer > Import... > General > Existing Projects into Workspace"

Tips and tricks

JDK required by the Maven plugin

Note that eclipse must start on a JDK to run Maven (among others) correctly. One way to do that is to add the -vm option in the eclipse.ini file that is in the eclipse installation folder.

-vm
C:/dev/Java/jdk1.6.0_17/bin/javaw.exe

Please note that

  • variable and path must be on 2 different lines
  • on windows, you must use / and not \ for the path.

Further action to remember to build an environment from scratch on windows

For maven to run correctly in command line :

-> set the JAVA_HOME variable in your environment to match the location of your java installation

-> add the path to apache-maven/bin directory to PATH variable

Some projects might required Python to build correctly. Version used is currently 2.6.5. add the path to corresponding install directory to PATH variable

Personal tools