Remove Snapshot dependencies

[amedranogil]

remove snapshot dependencies like :
org/springframework/osgi/log4j.osgi/1.2.15-SNAPSHOT/log4j.osgi-1.2.15-SNAPSHOT.pom
also look for any dependency not residing in the official repositories.

[amedranogil]

As discussed in
http://forum.spring.io/forum/attic/spring-dynamic-modules/73541-spring-osgi-test-1-2-0-log4j-osgi-1-2-15-snapshot

it seems the dependency is an embedded dependency in the springframework. They propose an alternative: to move to version 2.0.0.M1, which is no where to be found.

The maven command to get the dependency downloaded is:

mvn dependency:get -DartifactId=org.springframework.osgi -DgroupId=log4j.osgi -Dversion=1.2.15-SNAPSHOT -DremoteRepositories=uaal::default::http://depot.universaal.org/maven-repo/releases/,uaal-snapshot::default::http://depot.universaal.org/maven-repo/snapshots/,uaal-p1::default::http://nexus.lst.tfo.upm.es/content/groups/public/

[amedranogil]

To remove we must rethink, and redevelop itests. Vote this comment for option:

Maven-junit4OSGi-plugin

A Maven plugin that handles the integration testing of OSGi artifacts

Pros

• Integrates with Maven
• could integrate with our current workflow: question is if the list of bundles to deploy could handle a composite file (which it should).
• the whole itest repo could be removed

Cons

• The configuration of the test is long (it must include the custom configurations of the container for universAAL), and it must be declared on the pom of each module which uses it.
• It seems not to be possible to provide a custom config folder.

[amedranogil]

To remove we must rethink, and redevelop itests. Vote this comment for option:

OPS4J Pax Exam 4.x

A testing framework which allows for OSGi testing. Recommended by Karaf for integration testing.

Pros

• Maven integrable, through Alta Maven Plugin
• it is capable of running Karaf. Infact it should be able to run universAAL's distro.karaf
  • Removing the need to have to maintain different config folders.
  • Tests Karaf features
• Could be used to create new itest framework.
• it provides the hability of running independent tests in osgi environment (each test is like an activator.start() only executed in testing phase)

Cons

• it integrates with Maven, but it seems not to be trivial.
• it is very flexible, but very complex.
• The whole itest would need to be redeveloped.

[amedranogil]

To remove we must rethink, and redevelop itests. Vote this comment for option:

Enroute's Integration Testing

A framework which wraps Junit tests as OSGi bundles.

Pros

• Integrates with Maven
• it provides the hability of running independent tests in osgi environment (each test is like an activator.start() only executed in testing phase)

Cons

• Configuration of multi-bundle senarios seems complex and parallel to our workflow (composite vs parsii.bndrun)

[cstockloew]

Even though springframework 2.0.0.M1 was not found in any repo, we should still include it in this vote, because higher versions should be available on Maven Central. It may be the easiest, because we use it already, although there are probably a lot of changes. But it worked so far without bigger problems..
Current version: 5.0.x