From c319b33c3a36aa67addd7b089a9d871ab7a2d5b9 Mon Sep 17 00:00:00 2001 From: mindthegab Date: Wed, 9 Jul 2008 12:41:51 +0000 Subject: [PATCH] removed .project git-svn-id: http://maven-alfresco-archetypes.googlecode.com/svn/trunk@15 04253f4f-3451-0410-a141-5562f1e59037 --- maven-alfresco-extension-archetype/.project | 26 --------------------- 1 file changed, 26 deletions(-) delete mode 100644 maven-alfresco-extension-archetype/.project diff --git a/maven-alfresco-extension-archetype/.project b/maven-alfresco-extension-archetype/.project deleted file mode 100644 index 270cc12f..00000000 --- a/maven-alfresco-extension-archetype/.project +++ /dev/null @@ -1,26 +0,0 @@ - - maven-alfresco-extension-archetype - This archetype developed within Sourcesense aims to provide a standardized approach to development, release and deployment of Alfresco extensions (as opposed to AMP builds, to be released as a different artifact ). - Using standard m2 lifecycle commands (mvn compile package deploy) and generally available plugins (cargo, release, assembly) - we are able to cover a very high percentage of Alfresco lifecycle common use cases. - It can be used both with Maven2 and Ant build systems, but it must be clear that *only* the Maven2 approach provides all the - automation features we will describe in this website. - In addition to that the m2 approach provides a zero-conf approach while ant requires (as usual) manual gathering and - selection of required alfresco libraries and webapp (please refer to README-ant.txt for further info about the Ant - build). - Last but not the least, m2 build is more likely to be maintained and improved (especially in the likely case Alfresco moves to - maven2). For more details on the m2 apprach please refer instead to README Section (or directly and to README-m2.txt of the generated project). - - - - org.eclipse.jdt.core.javabuilder - - - org.maven.ide.eclipse.maven2Builder - - - - org.eclipse.jdt.core.javanature - org.maven.ide.eclipse.maven2Nature - - \ No newline at end of file