[Building Sakai] Generating Eclipse files from a SVN checkout.

[Matthew Buckett]

http://jira.sakaiproject.org/browse/SAK-16273

Ok the eclipse files should be gone from both trunk and 2.7.x now with
the svn:ignore set appropriately. To regenerate all the Eclipse files
the simplest command to run at the top of a checkout is:

mvn eclipse:clean eclipse:eclipse

This will regenerate very similar Eclipse files to the previous ones
and should be reasonably fast to run. It will also link project
references together so that related projects depend on each other
rather than the artifacts in you local maven repo.

Other options:

If you want to have Javadocs/sources available for artifacts where
possible use, but this increases the time of the run and and amount to
artifacts downloaded:

mvn eclipse:clean eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true

If you don't want eclipse files generated for all the projects (eg use
develop using a smaller working set) then the profiles should work
fine:

mvn eclipse:clean eclipse:eclipse -Pcafe

If you only are working on a small part of Sakai and don't want to
have to import the whole shebang then just run the command in a
project:

cd velocity
mvn eclipse:clean eclipse:eclipse

This will just generate projects for velocity with all the other
artifacts pointing at your local maven repo. If you then want to
generate the eclipse project files for site-manage but want to use the
existing velocity projects in your workspace you can do this with:

cd site-manage
mvn eclipse:clean eclipse:eclipse
-Declipse.projectDir=/full/path/to/eclipse/workspace

More details about the maven eclipse plugin can be found at:
http://maven.apache.org/plugins/maven-eclipse-plugin/index.html

or you can add Maven support directly into eclipse with m2eclipse (I
haven't used this):
http://m2eclipse.sonatype.org/

-- 
  Matthew Buckett
  VLE Developer, LTG, Oxford University Computing Services