inteligr8/alfresco-sdk
1
0
Fork 0
mirror of https://github.com/Alfresco/alfresco-sdk.git synced 2025-05-26 17:25:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

removed .project

Browse Source 
git-svn-id: http://maven-alfresco-archetypes.googlecode.com/svn/trunk@15 04253f4f-3451-0410-a141-5562f1e59037
This commit is contained in:
mindthegab 2008-07-09 12:41:51 +00:00
parent b2192837e5
commit c319b33c3a
1 changed files with 0 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
maven-alfresco-extension-archetype/.project
View File

@ -1,26 +0,0 @@
<projectDescription>
<name>maven-alfresco-extension-archetype</name>
<comment>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).</comment>
<projects/>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
</buildCommand>
<buildCommand>
<name>org.maven.ide.eclipse.maven2Builder</name>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.jdt.core.javanature</nature>
<nature>org.maven.ide.eclipse.maven2Nature</nature>
</natures>
</projectDescription>