Stop tracking jLinda - jLinda now an artifact/dependency

- jLinda is now used in NEST as separate dependency/artifact

- jLinda artifacts are distributed via maven.ppolabs.me

    Dependency for the core functionality:

        <dependency>
           <groupId>org.jlinda</groupId>
           <artifactId>jlinda-core</artifactId>
           <version>0.5</version>
        </dependency>

    Dependency for NEST operators:

        <dependency>
           <groupId>org.jlinda</groupId>
           <artifactId>jlinda-nest</artifactId>
           <version>0.5</version>
        </dependency>

- jLinda and NEST can still be jointly compiled

    1) jLinda source tree should be sourced into NEST. Preferably,
    using git-submodules, or simply by copying jLinda tree into NEST.

      For example invoking:

        $ git submodule add git@github.com:ppolabs/jlinda.git

      in top of NEST tree, will create jLinda module within NEST, that can
      be tracked and maintained as independent project.

    2) For compiling there are two (identical) profiles added to the central
    pom.xml of NEST: 'jlinda' and 'insar'

      Command to compile NEST and jLinda together:

        $ mvn compile -P insar
oops removed accidentally tracked submodule
jlinda version -> 0.6-SNAPSHOT
still removing submodule leftovers
Merge pull request #16 from pmar/unstable

Unstable