[Clas12_software] maven and travis integration

[Andrey Kim]

Dear all,

Following this morning meeting discussion allow me to suggest an 
approach that involves Travis+Maven integration. It should be easy to 
configure Travis scripts to deploy built jar files to maven repository 
(to clasweb/clas12maven at the moment, and to the public one, once we 
have it). This way we will always have jar file for each development 
branch as well as for master branch in the repository. Then switching 
your code dependencies to any particular branch would be as easy as 
copy/paste a few lines into pom.xml file.

To make it even easier we can have an overview page (just as any major 
maven repository has) to display what branches/versions are available 
online in the repository. Here is an example how this page would look 
like: https://clas12mon.jlab.org/maven/

In the future when/if we decide to separate reconstruction engines from 
common tools (as Vardan suggested, and I support) this kind of page 
would be even more useful to track different artifacts (i.e. packages).

Let me know what you think,

Andrey.

P.S. Useful link from official Travis CI page that explains how to 
configure Travis to deploy maven to repo.
https://blog.travis-ci.com/2017-03-30-deploy-maven-travis-ci-packagecloud/