Bugzilla Bug 6942

Goal: ease use of Yanel with Eclipse.

Small XSLT to help generating .classpath added in 41238: still rough, but can
be used manually as follows:
xsltproc --stringparam M2-repo-dir /home/guillaume/.m2/repository --stringparam
dependencies-doc-URL $PWD/dependencies.xml /path/to/dependencies2classpath.xslt
.classpath > .classpath2

Caution: xsltproc does not deal well with overwriting input files, that's why
.classpath2 is used instead of .classpath...

Also it seeems like all needed dependencies to compile the whole code are not
always there, so you might still have to add a few JARs manually! :/

In particular JUnit JAR is not here (rightfully: it's only useful for testing,
not for compiling or running): we should add a reference in the XSLT to
tools/apache-ant_extras/junit-3.8.1.jar (at least that's what the Yanel project
uses, dunno about others).

> Caution: xsltproc does not deal well with overwriting input files, that's why .classpath2 is used instead of .classpath...

Somehow workarounded in 41728, as a default .classpath input document can now
be used.

New usage:
xsltproc --stringparam M2-repo-dir /home/guillaume/.m2/repository
~/public-Wyona.onlyFiles.VC/0_tools/eclipse-3.settings/dependencies2classpath.xslt
src/build/dependencies.xml > .classpath2

Found (revision 41913 and revision 41914) a hopefully final solution for
generating .classpath files which unlike the former handle transitive
dependencies and so gets the full needed classpath.

There are still problems (the Yanel-specific base test classes are not in the
classpath) so leaving this open.

> [...] the Yanel-specific base test classes are not in the classpath

Solving this required a refactoring of the Yanel JAR installation code: done in
revision 41922.

...and also revision 41956.

...and also revision 41958 which fixes the broken build! :/

Thanks to revision 41961 all the files needed for a compilable Eclipse project
can now be generated using a simple command: `build -f ... eclipse`! :)

Since revision 42121 the Yanel test project can now also be compiled easily in
Eclipse!

Since revision 42181 the Yanel test project can now also be compiled easily in
Eclipse!


Allowing these projects to compile under Eclipse also allows source-level
debugging with hot code replacement from Eclipse: you can now change Java
methods' code (not signatures) of Yanel without restarting.

Alas for resource-types this is not possible yet (doing that for those under
${yanel.source.home} may be easier though).

> Since revision 42181 the Yanel test project can now also be compiled easily in
> Eclipse!

Oops, I meant the Yanel *webapp* project!

...and since revision 42975 that did not work anymore because of the splitting
of the Neutron stuff, fixed in revision 43282.

Since revision 43713 the Wyona Commons project can now also be compiled easily
in
Eclipse!

Since revision 43912 the Wyona Security project can now also be compiled easily
in Eclipse!

Since revision 43914 Yanel subprojects now always have their source code
attached under Eclipse! :)

Since r44922 the Wyona Yarep project can now also be set up automatically for
Eclipse!

Since r44993 all realms (that have a specific Ant build script and so probably
have some Java classes to compile) can potentially be set up automatically for
Eclipse!
Also this has been done for all such non-contributed Yanel realms, i.e. the
Welcome Admin realm and the Yanel website realm.

Since r48178 all resource-types specific to a given realm (e.g. those defined
in $REALM_DIR/resource-types.xml) can be imported in one go as Eclipse
projects!