| | 1 | == Maven Repository == |
| | 2 | |
| | 3 | The BRICCS Maven repository is currently (December 2010) a Maven2 repository.[[BR]] |
| | 4 | |
| | 5 | 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.[[BR]] |
| | 6 | |
| | 7 | 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. |
| | 8 | |
| | 9 | === Ideas for a Naming Standard === |
| | 10 | We need to differentiate between: |
| | 11 | * Artifacts which have gone live; ie: the source is tagged within SVN. These could be historical as well as currently live versions. |
| | 12 | * Artifacts built from source at the trunk within SVN; ie: developed but not deployed in a live environment yet. |
| | 13 | |
| | 14 | 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: |
| | 15 | * Artifacts built from tagged versions within SVN (ie official releases) should have the standard version numbering system. |
| | 16 | * Artifacts built from the trunk (but not yet released as official versions) should have SNAPSHOT within the name. |
| | 17 | |
| | 18 | 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. |
| | 19 | |
