From 047c05032ccde4dd147f2670a79f1421c2b26616 Mon Sep 17 00:00:00 2001 From: maoo Date: Thu, 3 Jul 2014 10:00:59 +0000 Subject: [PATCH] issue #108 fixed; removed outdated README and ROADMAP txt git-svn-id: http://maven-alfresco-archetypes.googlecode.com/svn/trunk@743 04253f4f-3451-0410-a141-5562f1e59037 --- plugins/alfresco-maven-plugin/README.txt | 100 ---------------------- plugins/alfresco-maven-plugin/ROADMAP.txt | 22 ----- 2 files changed, 122 deletions(-) delete mode 100644 plugins/alfresco-maven-plugin/README.txt delete mode 100644 plugins/alfresco-maven-plugin/ROADMAP.txt diff --git a/plugins/alfresco-maven-plugin/README.txt b/plugins/alfresco-maven-plugin/README.txt deleted file mode 100644 index 538abe23..00000000 --- a/plugins/alfresco-maven-plugin/README.txt +++ /dev/null @@ -1,100 +0,0 @@ -*************** -What does it do -*************** - -The alfresco-maven-plugin provides the following features: - -* Packages an AMP starting from a simple (and configurable) Maven project folder structure -* Performs AMP to WAR overlay by using the Alfresco Repository ModuleManagementTool and emulating the same process -during Alfresco boostrap - - -***** -Usage -***** - -+ In order to build an AMP file, you must: ----- - -1. Define your POM as amp - -2. Specify a module.properties file in the src/main/amp folder, containing the following properties: -module.id=${project.artifactId} -module.title=${project.name} -module.description=${project.description} -module.version=${project.version} -As you can see, the file is filtered with Maven project placeholders - -3. Declare the alfresco-maven-plugin in your POM build section - - - - - org.alfresco.maven.plugin - alfresco-maven-plugin - 0.7-SNAPSHOT - - - ... - - -Always keep in mind the default project-to-AMP mapping: -* src/main/amp => / -* src/main/resources => /lib/amp-classes.jar -* src/main/java => /lib/amp-classes.kar - - -+ In order to overlay an existing Alfresco WAR file, you'll need the following elements: ----- - -1. Define the type of Alfresco WAR you want to overlay: share or alfresco - - - share - - -2. Define the following build behaviour - - - - - org.apache.maven.plugins - maven-dependency-plugin - - - unpack-alfresco - prepare-package - - unpack - - - ${project.build.directory}/${project.build.finalName} - - - ${alfresco.groupId} - alfresco - war - ${alfresco.version} - - - - - - - - - - org.alfresco.maven.plugin - alfresco-maven-plugin - - - amps-to-war-overlay - prepare-package - - install - - - - - - \ No newline at end of file diff --git a/plugins/alfresco-maven-plugin/ROADMAP.txt b/plugins/alfresco-maven-plugin/ROADMAP.txt deleted file mode 100644 index b1a4e02b..00000000 --- a/plugins/alfresco-maven-plugin/ROADMAP.txt +++ /dev/null @@ -1,22 +0,0 @@ -SHORT TERM (TODO): -* Review of the module.properties version replace. Can't it be just using resource filtering? -(i.e. a more similar approach to the buildnumber or nosnapshot plugin) -* Review the amp-to-war profile. When ran from an AMP project abuses of - the project.build.directory/project.build.finalName folder (both AMP and WAR content in there) -* Documentation -* Full release - - Alfresco POMs - - Developer & Parent POMs - - Archetypes - - Test test test - -MID TERM -* Validate module.properties : make sure all properties are there and version is correct; if not, fix it -* Fail if module-context.xml is not present -* Implement and configurations; based on that, the alfresco WAR dependency will be -included into the POM at runtime by the add-resources goal -* Test coverage (unit first, use mocking) -* Test AMP install with extensions from addons.alfresco.com -* Release alfresco-maven-plugin (on git - maven-alfresco-archetypes on Google Code) -* Finalize documentation and publish it (wiki.alfresco.com) -* Evaluate running JMeter Maven plugin in order to launch Alfresco test suites