Author: brett
Date: Wed Dec  2 04:52:12 2009
New Revision: 886049

URL: http://svn.apache.org/viewvc?rev=886049&view=rev
Log:
[MRM-1025] add references to the content model

Modified:
    archiva/branches/MRM-1025/archiva-modules/metadata/content-model.txt

Modified: archiva/branches/MRM-1025/archiva-modules/metadata/content-model.txt
URL: 
http://svn.apache.org/viewvc/archiva/branches/MRM-1025/archiva-modules/metadata/content-model.txt?rev=886049&r1=886048&r2=886049&view=diff
==============================================================================
--- archiva/branches/MRM-1025/archiva-modules/metadata/content-model.txt 
(original)
+++ archiva/branches/MRM-1025/archiva-modules/metadata/content-model.txt Wed 
Dec  2 04:52:12 2009
@@ -18,7 +18,7 @@
         |                   |   |   |   |-- asc=
         |                   |   |   |   |-- created=
         |                   |   |   |   |-- maven:buildNumber=
-        |                   |   |   |   |-- maven:classifier=
+        |                   |   |   |   |-- maven:classifier
         |                   |   |   |   |-- maven:timestamp=
         |                   |   |   |   |-- maven:type=
         |                   |   |   |   |-- md5=
@@ -87,12 +87,44 @@
         |                   |   |   `-- url=
         |                   |   `-- maven:artifactId=
         |                   `-- maven:groupId=
-        `-- metadata/
+        `-- references/
+            `-- org/
+                `-- apache/
+                    `-- archiva/
+                        |-- parent/
+                        |   `-- 1/
+                        |       `-- references/
+                        |           `-- org/
+                        |               `-- apache/
+                        |                   `-- archiva/
+                        |                       |-- platform/
+                        |                       |   `-- scanner/
+                        |                       |       `-- 1.0-SNAPSHOT/
+                        |                       |           `-- 
referenceType=parent
+                        |                       `-- web/
+                        |                           `-- webapp/
+                        |                               `-- 1.0-SNAPSHOT/
+                        |                                   `-- 
referenceType=parent
+                        `-- platform/
+                            `-- scanner/
+                                `-- 1.0-SNAPSHOT/
+                                    `-- references/
+                                        `-- org/
+                                            `-- apache/
+                                                `-- archiva/
+                                                    `-- web/
+                                                        `-- webapp/
+                                                            `-- 1.0-SNAPSHOT/
+                                                                `-- 
referenceType=dependency
+
 
 (To update - run "tree --dirstfirst -F" on the unpacked content-model.zip from 
the sandbox)
 
 Notes: 
 
+*) config should be reflected to an external configuration file and only 
stored in the content repository for purposes
+   of accessing through a REST API, for example
+
 *) In the above example, we have the following coordinates:
    - namespace = org.apache.archiva.platform (namespaces are of arbitrary 
depth, and are project namespaces, not to be
                                               confused with JCR's item/node 
namespaces)
@@ -133,7 +165,7 @@
 *) created/updated timestamps may be maintained by the metadata repository 
implementation
 
 *) references are stored outside the main model so that their creation doesn't 
imply a "stub" model - we know if the
-   project exists whether a reference is created or not. References need not 
infer referential integrity
+   project exists whether a reference is created or not. References need not 
infer referential integrity.
 
 *) some of the above needs to be reviewed before going into production. For 
example:
    - the maven specific aspects of dependencies should become a faceted part 
of the content


Reply via email to