mirror of
https://github.com/Alfresco/alfresco-sdk.git
synced 2025-08-07 17:49:34 +00:00
added project history and few minor documentation fixes
git-svn-id: http://maven-alfresco-archetypes.googlecode.com/svn/trunk@642 04253f4f-3451-0410-a141-5562f1e59037
This commit is contained in:
@@ -97,7 +97,7 @@ Overlay and installation of AMPs to WAR
|
||||
|
||||
** Multiple AMP installation
|
||||
|
||||
The plugin is thoroughly documented in the {{{./install-mojo.html} mojo page}}, but we provide here an example of how to mimic the
|
||||
The plugin installation goal is thoroughly documented in the {{{./install-mojo.html} alfresco:install mojo page}}, but we provide here an example of how to mimic the
|
||||
<<<apply_amps.sh>>> (Alfresco script), using the Alfresco Maven Plugin to install a full folder of AMPs (<<NOTE:>> The install goal
|
||||
is bound in this case to the <<<package>>> phase, it's up to you to make sure an exploded WAR or WAR is present in warLocation
|
||||
during that phase):
|
||||
|
@@ -18,7 +18,7 @@ Introduction
|
||||
|
||||
*{{{./install-mojo.html}alfresco:install}} Installs one or multiple AMPs into an Alfresco WAR / exploded WAR folder embedding {{{http://wiki.alfresco.com/wiki/Module_Management_Tool} Alfresco MMT}}
|
||||
|
||||
*{{{./set-version-mojo.html}alfresco:version}} Parses ${project.version} removing literals (for AMP compatibility) and making the <<<$\{noSnapshot\}>>> property available in the POM
|
||||
*{{{./set-version-mojo.html}alfresco:version}} Parses ${project.version} removing literals (for AMP compatibility) and making the <<<$\{noSnapshotVersion\}>>> property available in the POM
|
||||
|
||||
More info in the {{{./plugin-info.html}goals page}}.
|
||||
|
||||
|
@@ -1,11 +1,11 @@
|
||||
-----
|
||||
Alfresco Maven Plugin Components
|
||||
-----
|
||||
The Alfresco Maven Plugin defines support components to manage AMP (Alfresco Module Package) lifecycle.
|
||||
-----
|
||||
Alfresco Maven Plugin Components
|
||||
-----
|
||||
The Alfresco Maven Plugin defines support components to manage AMP (Alfresco Module Package) lifecycle.
|
||||
|
||||
AMP Lifecycle
|
||||
AMP Lifecycle
|
||||
|
||||
This plugin provides support for <<<<packaging>amp</packaging>>>> type of projects. \
|
||||
This plugin provides support for <<<<packaging>amp</packaging>>>> type of projects.
|
||||
|
||||
The lifecycle of an <<<amp>>> follows:
|
||||
|
||||
@@ -30,16 +30,16 @@
|
||||
</component>
|
||||
+---+
|
||||
|
||||
This build produces an Alfresco compatible AMP as main build product.
|
||||
|
||||
AMP -> WAR Unarchiver
|
||||
This build produces an Alfresco compatible AMP as main build product.
|
||||
|
||||
AMP -> WAR Unarchiver
|
||||
|
||||
A Plexus UnArchiver (<<<role-hint="amp">>>) is configured to be used by default by Maven for AMP dependencies.
|
||||
This UnArchiver invokes the MMT therefore allowing proper AMP installation according to {{{http://wiki.alfresco.com/wiki/AMP_Files} convention}} .
|
||||
This component allows any plugin to manage <<<amp>>> dependencies and in particular enables AMPs to be used as part
|
||||
of the standard maven-war-plugin <<<<overlay>>>> section.
|
||||
|
||||
AMP Artifact Handler
|
||||
|
||||
AMP Artifact Handler
|
||||
|
||||
Instructs maven which type of Archive is the AMP, providing info about its inclusion in the classpath or the fact that already contains
|
||||
its dependencies.
|
||||
|
Reference in New Issue
Block a user