z2-Environment

h1. Maven Repos Support

The main idea behind this concept is to hook existing Maven repositories in as component repositories. At first this is most useful for libraries, later this may be extended to other archetypes.

Maven repository suppport can be implemented in z2-base and does not require core changes.

h2. Name mappings

Artefacts in Maven repos have a fully qualified name of the form 

<pre>

<groupId>:<artifactId>:<version>

</pre>

where <groupId> is something like *org.acme*, <artefactId> is something like *mylibrary* and <version> is a fully structured _major.minor.micro_ style version or a version that has an appended "-SNAPSHOT" qualifier indicating an non-well-defined version that may receive intermediate updates.

When exposed via a Z2 component repository Maven artefacts will be addressed by their fully qualified name as module name and with an archetype specific in-module component name.

E.g. a library of packaging jar, will translate to 

<pre>

<groupId>:<artefactId>:<version>/jar

</pre>

In order to simplify management of version vectors, the [[smart_props]] approach may be utilized.

Dependencies of Maven repo artefacts get mapped to Java dependencies, for the case of the jar archetype after parsing a corresponding POM file.