[maven-release-plugin] copy for tag maven-alfresco-lifecycle-1.1.0

#    See the License for the specific language governing permissions and

#    limitations under the License.

ISSUES:

-------

- tools/mysql folder scripts are copied over the classpath (because of the filtering feature, shall we remove it?). It's harmless anyways apart from the potential secuity issues (BTW credentials are deployed non encrypted anyways in application.properties)

- fix commented library versions

TODO (in order of priority):

-----

- AMP archetype

- make jetty:run-inplace work for easy runtime editing

- translate other TXT files into APT for maven site generation (as done for README)

- Integration testing with selenium

- unit testing suite

 No newline at end of file

- Configure class/contexts reloading for jetty run

- add multimodule support (and extract release/deploy policies to a super POM for usage also by AMP archetype)

- add amp dependency mgmt or let steer alfresco for a jar artifact (jsp loading from jar or pre extracted?)

- move archetype documentation in mvn site

 No newline at end of file

What can this build do?

  This Maven Alfresco build process allows you to develop, test, run, document and release your Alfresco extension project.

  You can also depend on AMP files deployed on a Maven repository (either manually or using the Maven Alfresco AMP archetype),

  by adding the following <<< <dependency> >>> snippet to your Extension pom.xml:

  This Maven Alfresco build process allows you to :

  * develop and package

  * test and run (on different platforms)

  * document and release your Alfresco extension project (site and PDF documentation)

  * You can also depend on AMP files deployed on a Maven repository (either manually or using the Maven Alfresco AMP archetype),

  by adding the following <<< dependency >>> snippet to your Extension pom.xml:

--------------------------------------------

   <dependency> 

   </dependency>

--------------------------------------------

  This operation will result in automated AMP unpacking in your Extension WAR file during the normal build process (e.g. mvn package or mvn install).

  This operation will result in automated AMP unpacking in your Extension WAR file during the normal build process (e.g. <<<mvn package>>>).

Configuration:

  The project created from the extension archetype is very flexible. It uses a configuration mechanism (pre 3.2) which sigles sources

  the all required properties in one single file (called <<<application.properties>>>) which is global to the whole Spring context.

  This works also against 3.2, but activities are ongoing to converge to a proper usage of the new <<<alfresco-global.properties>>. 

  The project created from the extension archetype is very flexible. It uses a configuration mechanism (pre 3.2) which sigles sources the all required properties in one single file (called <<<application.properties>>>) which is global to the whole Spring context.

  This works also against 3.2, but activities are ongoing to converge to a proper usage of the new <<<alfresco-global.properties>>>. 

  Properties are stored in the <<< src/main/properties/<env> >>> folders and env=local is considered by default. You can switch the environment

  you're building for (e.g. for a release) using the <<<-Denv=yourEnv>>> switch in the command line build.