Get rid of maven for defining classpath

[sfrank]

Changing the classpath for a component is currently a two-step-process:

• trigger a manual rebuild of the classpath via antlib/resources/maven.xml
• trigger the normal build with the updated classpath

This two-step-process is error-prone, especially on windows. To reduce the number of moving parts in the build, the manual classpath-build should be included in the regular build and changed classpaths should be picked up automatically whenever the build is run.

[jmoore]

I don't think anyone is overly happy with the current situation. Maven has not proved to be the best tool here. However, we currently have this setup, even if it's not working (well) on Windows. If you can port to Ivy, etc., then by all means, that's fine.

Requirements are:

1. Central definition. One should only have to change one file to change the classpath. (No changing pom.xml, .classpath, and ivy.xml or whatever)
2. Transitive dependencies. We should only have to define our direct dependencies.
3. Definition inheritance. Global definitions should be done at the OMERO_HOME level with a definition done for each component as well.
4. Components must remain isolated, based on their dependency graph.
5. No run-time overhead. Once it's working, it shouldn't hit the network anymore.

Bonus: version numbers should be stored externally (in *.properties)

[jmoore]

#45, #98, and #101 are dependent on this ticket.

[jmoore]

See #749

[jmoore]

Can be considered closed with the closing of #749. Classpaths are now defined by the contensts of <component>/target/libs.