Maven Repository

The BRICCS Maven repository is currently (December 2010) a Maven2 repository.

The repository is important because it gives access to already built BRICCS artifacts. That is, a development environment is not required in order to build an artifact before deploying it in a live or test environment (eg: within Tomcat or JBoss); rather, an already built versioned artifact should be available from the maven repository.

Over time it may also give access to third party artifacts (acting as a mirror for other publicly available repositories), but that is not the case at present.

Ideas for a Naming Standard

We need to differentiate between:

• Artifacts which have gone live; ie: the source is tagged within SVN. These could be historical as well as currently live versions.
• Artifacts built from source at the trunk within SVN; ie: developed but not deployed in a live environment yet.

Some organizations run two repositories to differentiate these levels. This seems a little too much for the level of BRICCS development at present, so I suggest:

• Artifacts built from tagged versions within SVN (ie official releases) should have the standard version numbering system.
• Artifacts built from the trunk (but not yet released as official versions) should have SNAPSHOT within the name.

For instance, the unique id generator might have releases briccs-uidgen-1.0.jar and briccs-uidgen-1.0.1.jar, whereas the very latest source would (if it has been deployed within maven) have an unreleased artifact of briccs-uidgen-n.n.n-SNAPSHOT.jar where n.n.n is the proposed next version number proposed for its release.