Created OSPF actionset skeleton.

OSPFActionSet class contains actions to manage OSPF.
blueprint/core.xml has been updated to export OSPFActionSet as a service.

Actions are not implemented (they are stubs).
Fix error with mapping between Action name and Action implementation in OSPF ActionSet.

This error caused ConfigureOSPFAction to be called when OSPF_GET_CONFIGURATION was requested.
It also caused GetOSPFConfigAction to be called when OSPF_CONFIGURE was requested.

Mapping has been changed to achieve desired behavior.
build: Refactor Maven project files

The patch

- Moves all version numbers to distributionManagement and
  pluginManangement sections. This means that a version
  number of a plugin or dependency is stored in one place.
  For external dependencies the version is moved to the
  top level pom file.

- Moves the version number of internal dependencies to
  distributionManagement sections. In contrast to the
  external dependencies, these version numbers are stored
  in the inner most pom that still covers all uses of
  the dependency. Ie opennaas artifacts are in the top
  level pom, manticore artifacts in the manticore pom,
  and test artifcats in the test pom. This also nicely
  ensures that we don't refer to, say, a test artifact
  from outside the tests.

  The internal dependencies are parameterized to use the
  project version number.

- All projects are updated to inherit the version number
  from the top level project.

- Use the project.version property rather than a
  hardcoded value in paths.

- Use project.version rather than pom.version (pom.version
  is deprecated).

- Removes redundant parts of the project files:

   - sourceEncoding is defined once in the top level
     pom and inherited

   - Redudant or unused <resources> declarations are
     removed (the defaults are usually fine - and Maven
     is a about convention over configuration).

   - Repeated repository references are removed.

   - Repeated dependencies and plugins
build: Move Eclipse lifecycle configuration to top-level pom

Submodules inherit the configuration, so no need to repeat it
over and over.
build: Upgrade assembly plugin and enable tar support for long filenames

This gets rid of the build warnings about paths being longer than 100
characters.

The new version required minor changes in the assembly descriptors.
build: Upgrade Maven plugins to latest versions

Upgrade several Maven plugins to more recent versions.
build: Update dependencies to more recent releases
build: Fix pax exam2 dependencies

It is important that tests that run on pax exam2 do not
accidentally pull in pax exam 1 components.

Pulling the framework in as a dependency is recommended
in the karaf test container documentation and it speeds
up test execution.
tests: Let net.i2cat.nexus.resources.tests use injection

The patch cleans up the net.i2cat.nexus.resources.tests (currently
the only tests using the KarafTestContainer) such that dependency
injection is used to obtain references to other services.

The patch also removes the polling code and delay to wait for
other services. The intention with that code was to give the
blueprint containers time to start and thus ensure that
repositories and capabilities needed for the tests had been
loaded. It is faster and more robust to instead inject the
blueprint container reference into the test. This ensures that
the test isn't executed until the required blueprint container
has finished initilization. The added benefit is to make the
dependency explicit in the code.

Please note that I do not guarantee that I recognized all
dependencies. If you see the tests fail non-deterministically
then please tell me so we can add all dependencies.
tests: Port net.i2cat.luminis.tests.commandsKaraf to pax-exam 2

Also uses Injection to obtain references to other services and
to express dependencies on blueprint containers.
features: Fixed coordinates of nexus-test-helper

The URI was incorrectly formatted.
nexus.test.helper: Make pax-exam1 optional

The net.i2cat.nexus.test.helper package contains utility
classes useful for testing. The package was unusable with
pax-exam2 because it required pax-exam1 to be loaded.

This patch makes the pax-exam1 dependency optional. Thus
remaining classes from the package can be used with pax-exam2.
This workaround can be removed once all tests have been
transitioned to pax-exam2.
tests: Port spring0_2 to pax-exam2
tests: Port net.i2cat.mantychore.tests.commandsKaraf to pax-exam2
Merge branch 'feature/cleanup-build' of git://github.com/gbehrmann/opennaas into develop
Refactored GetConfigurationAction for better readability.
tests: Port sprint0_3 to pax-exam2
tests: Ported sprint0_4 to pax exam 2
build: Parameterize version numbers in OpenNaaS feature repository
tests: Port weeb26 tests to pax exam 2

Note that the tests are not actually included in OpenNaaS/Manticore
(they are commented out of manticore/tests/sprints/pom.xml). I assume
this is because the tests are failing.

One of the ported tests still fails (InterfacesVLANKarafTest). As
far as I can see this is because the test is buggy. It fails with:

[ERROR] the command encapsulation is limited in logical tunnels