just created a file
now with some real text
Added some authors
Merge branch 'develop' of github.com:dana-i2cat/opennaas into feature/readme-file
remove "commit" file
Added real authors.
Merge branch 'develop' into feature/cleanup-integration-test-poms
tests: Port ospf and gre tunnel tests to pax exam 2

I also updated tests to not catch all failure exceptions
explicitly. JUnit will by default consider them test
failures and log a stack trace.
build: Revert accidental change of parent in BoD integration test

In the previous commit I accidentally changed the parent of one of the
existing integration tests projects. This patch reverts the change.
Merge branch 'feature/port-remaining-tests-to-pax-exam2' into feature/cleanup-integration-test-poms

Conflicts:
	manticore/pom.xml
Merge pull request #39 from gbehrmann/feature/port-remaining-tests-to-pax-exam2

Feature/port remaining tests to pax exam2
tests: Simplify opsf and gretunnel test projects

The patch updates the two new integration test projects
to follow the simpler Maven project structure made
possible by a pure pax exam 2 setup.
Merge pull request #34 from gbehrmann/feature/configure-release-plugin

Feature/configure release plugin
Merge pull request #28 from gbehrmann/feature/cleanup-integration-test-poms

Feature/cleanup integration test poms
Merge pull request #37 from dana-i2cat/feature/readme-file

Feature/readme file
build: Configure site module

In Maven 3 the site module needs to be configured to allow for
reporting plugins to work. This patch configures the site plugin.

The patch also configures various reports, including JavaDoc, source
code cross reference, find bugs analysis, pmd and cpd analysis.

I disabled a couple of slow reports, and generally chose aggregated
reports over individual reports.

I had to update the two platform projects to ensure that the
features-magen-plugin is executed in the correct phase (otherwise it
would conflict with the JavaDoc plugin).

The site report can be build by running:

    mvn clean install site

followed by

    mvn site:stage

The latter combines all reports into a single report structure in
target/staging/

Note that producing the reports will take a lot of memory and the
default Maven settings will not suffice. I set

    MAVEN_OPTS="-Xmx2048m -XX:MaxPermSize=1024M"

to solve this.
build: Remove redundant repository references

The parent poms already list all Maven repositories needed.
build: Sync lists of feature repositories

We refer to service mix feature repositories in three
different places:

- Our own feature repositories
- The features-maven-plugin
- The Karaf feature configuration file

Unfortunately this repetition cannot be completely avoided (even
though it breaks DRY).

This patch syncs the lists of feature repositories, ensuring that
the features we resolve at runtime are the same as the features
resolved by the maven plugin. Specifically this ensures that all
the bundles needed at runtime have been installed in the Karaf
system repository during build time.

As a consequence no extra bundles will be downloaded the first time
Mantychore is started. Thus Mantychore can now be started without
a network connection. Even more important, Mantychore integration
tests can be executed without a network connection. The integration
tests also finish significantly faster as all dependencies are
present in the test environment.

Note that I changed the configuration of the features-maven-plugin
to install dependencies too. By itself this change is however not
enough because the various feature repositories shipped with
ServiceMix have overlapping feature descriptors with inconsistent
dependencies. Thus before this patch the cxf repository resolved
at build time was different than the one resolved at runtime.
build: Remove activemq dependencies

Several bundles import activemq packages even though they
don't make use of it. These dependencies needlessly force
activemq to be loaded.
build: Refactor feature repositories

The OSGi feature repositories of OpenNaaS and Mantychore had
several problems:

- They were not self-contained in the sense that installing
  the feature required one to manually ensure that
  requirements had been installed before.

- They were split into a deps feature and a core feature. The
  deps feature was really a usable feature in itself; it simply
  embodied dependencies. The core feature on the other hand
  contained all features of the product. This didn't allow
  for selectively installing features of the product.

- Dependencies were not flagged as dependencies.

- Bundle version numbers were hardcoded.

- Some of the depenendencies are unnecessary (like activemq),
  and others are only used by periferal functionality (like
  cxf). Forcing these dependencies are pre-requisites means
  that integration testing becomes unnecessarily slow as
  all dependencies have to be started for every test.

This patch refactors the feature repositories.

- There are no longer any -deps features. Features are now
  self-contained with all dependencies specified. This means
  one can do 'feature:install x' and expect it to install all
  prerequisites.

- Features are split according to what one can consider
  "end-user features", eg router, network and bod are features,
  and so is junos. The core opennaas functionality is a feature
  too.

- All version numbers are parameterized.

- I tried to identify the essential dependencies of each feature.

Testing done: Unit and integration tests pass. I manually
installed each feature on a fresh build to verify that they
can resolve all bundle dependencies. I ran Mantychore and
configured it to connect to an Olive. I verified that basic
commands like creating logical routers and subintefaces work.