Add pom.xml to scala component

[imagejan]

This PR add a pom.xml to be able to build the scala component with maven. It would make it possible to easily deploy to a Maven repository, where other Maven-based projects can use it.

(this required moving the examples into src/test/scala/examples)

If this is acceptable, let me know if I should update the <developers> and <contributors> section according to the team role definitions.

[Ichoran]

Thanks! I'll review the PR shortly, but note that maven is an unusual choice for a build tool for Scala (sbt is typical), so I'm likely to take the details and port them to sbt instead to avoid requiring people to use multiple sets of tools to accomplish what can be done with one tool. (On the other hand, getting sbt to publish successfully is a bit of work; if the maven thing is substantially easier, maybe that's the way to go.)

[imagejan]

I chose maven just because I'm not so familiar with sbt and scala, but re-using the maven setup from pom-scijava helped me to get a deployable jar file without a hassle. Any other mechanism is fine of course, my main intent was to make this usable from Maven-based Java projects simply by adding something like:

<dependency>
    <groupId>org.openworm<groupId>
    <artifactId>tracker-commons<artifactId>
</dependency>

[Ichoran]

@imagejan - However we handle the logistics, having an artifact published on Maven would be great. I'll try to get it up this week. (I usually end up struggling with Sonatype for a good while before I get anything published, though.)

[MichaelCurrie]

this seems harmless enough, after 8 years perhaps we could just merge this. @pgleeson