The following subprojects exist within Archiva:\r
\r
* archiva-applet - The progress bar on the checksum checking page.\r
+\r
* archiva-configuration - A facade on top of the Plexus configuration XML.\r
+\r
* archiva-converter - converts an m1 repository to an m2 one - currently not hooked up\r
+\r
* archiva-core - central code, business objects, modello etc.\r
+\r
* archiva-discoverer - monitors the managed repositories and kicks off the indexing.\r
+\r
* archiva-indexer - the lucene indexing.\r
+\r
* archiva-plexus-application - archiva can run on plexus as well as as a war. This creates a plexus app.\r
+\r
* archiva-plexus-runtime - archiva can run on plexus as well as as a war. This runs lots of apps.\r
+\r
* archiva-proxy - proxies repositories?\r
+\r
* archiva-reports-standard - a couple of reports are implemented. Not very pluginable yet.\r
+\r
* archiva-repository-layer - a query layer for the reports\r
+\r
* archiva-security - webapp security\r
+\r
* archiva-utils - some handy archiva specific utils\r
+\r
* archiva-webapp - creates a war file\r
+\r
* design - contains a mock-up currently\r
+\r
* maven-meeper - rsync scripts to sync repositories. Also converts m1 repositories to m2 repositories.\r
\r
Concepts\r
There are various terms in Archiva that are worth explaining and defining. \r
\r
* "Managed" - A managed repository is a repository which Archiva is sitting on top of that may be browsed.\r
+\r
* "Indexed" - The ability to search a managed repository.\r
+\r
* "Proxied" - A remote repository which an existing managed repository can be used as a facade for.\r
+\r
* "Synchronized" - A remote repository which is physically copied down to be managed under Archiva. \r
+\r
* "Identifier" - A short ID for your repository that will be used in URLs.\r
<menu name="Documentation">
<item name="Welcome" href="/index.html"/>
<item name="Getting Started" href="/guides/getting-started/index.html"/>
+ <item name="Developing" href="/guides/developing/index.html"/>
</menu>
<menu ref="reports" inherit="bottom"/>