Author: jdcasey
Date: Fri Aug  7 20:11:30 2009
New Revision: 802166

URL: http://svn.apache.org/viewvc?rev=802166&view=rev
Log:
Consolidate the various excludes for files used by major IDEs, the release 
plugin, and other files that are generally excluded by SVN.

Modified:
    
maven/resources/trunk/apache-source-release-assembly-descriptor/src/main/resources/assemblies/source-release.xml

Modified: 
maven/resources/trunk/apache-source-release-assembly-descriptor/src/main/resources/assemblies/source-release.xml
URL: 
http://svn.apache.org/viewvc/maven/resources/trunk/apache-source-release-assembly-descriptor/src/main/resources/assemblies/source-release.xml?rev=802166&r1=802165&r2=802166&view=diff
==============================================================================
--- 
maven/resources/trunk/apache-source-release-assembly-descriptor/src/main/resources/assemblies/source-release.xml
 (original)
+++ 
maven/resources/trunk/apache-source-release-assembly-descriptor/src/main/resources/assemblies/source-release.xml
 Fri Aug  7 20:11:30 2009
@@ -24,17 +24,53 @@
     <format>zip</format>
   </formats>
   <fileSets>
+    <!-- main project directory structure -->
     <fileSet>
       <directory>.</directory>
       <outputDirectory>/</outputDirectory>
       <useDefaultExcludes>true</useDefaultExcludes>
       <excludes>
-        <exclude>%regex[(?!.*src/).*target.*]</exclude>
+        <!-- build output -->
+        <exclude>%regex[(?!.*src/).*${project.build.directory}.*]</exclude>
+        
+        <!-- NOTE: Most of the following excludes should not be required 
+             if the standard release process is followed. This is because the 
+             release plugin checks out project sources into a location like
+             target/checkout, then runs the build from there. The result is
+             a source-release archive that comes from a pretty clean directory
+             structure.
+             
+             HOWEVER, if the release plugin is configured to run extra goals
+             or generate a project website, it's definitely possible that some
+             of these files will be present. So, it's safer to exclude them.
+        -->
+             
+        <!-- IDEs -->
         <exclude>**/.settings/**</exclude>
         <exclude>**/.project</exclude>
         <exclude>**/.classpath</exclude>
+        <exclude>**/.externalToolBuilders/**</exclude>
+        <exclude>**/maven-eclipse.xml</exclude>
+        <exclude>**/.deployables/**</exclude>
+        <exclude>**/.wtpmodules/**</exclude>
+        <exclude>**/*.iws</exclude>
+        <exclude>**/*.ipr</exclude>
+        <exclude>**/*.iml</exclude>
+        <!-- misc -->
         <exclude>**/cobertura.ser</exclude>
+        <exclude>**/*.bak</exclude>
+        <exclude>**/*.diff</exclude>
+        <exclude>**/*.patch</exclude>
+        <exclude>**/*.log</exclude>
+        <!-- release-plugin temp files -->
+        <exclude>**/pom.xml.releaseBackup</exclude>
+        <exclude>**/release.properties</exclude>        
       </excludes>
     </fileSet>
+    <!-- license, readme, etc. calculated at build time -->
+    <fileSet>
+      
<directory>${project.build.directory}/maven-shared-archive-resources/META-INF</directory>
+      <outputDirectory>/</outputDirectory>
+    </fileSet>
   </fileSets>
 </assembly>


Reply via email to