Also, I've tried this with checkModificationExcludeList as well, with no difference.
Thanks, Ed ---------- Forwarded message ---------- From: Ed Hillmann <ed.hillm...@gmail.com> Date: Fri, Feb 17, 2012 at 8:08 AM Subject: Is checkModificationExcludes working for anyone? To: Maven Users List <users@maven.apache.org> Hi all. I'm trying to use the checkModificationExcludes attribute of the release:prepare goal, but it seems to be ignoring it. I'm using version 2.2.2 of the plugin. My pom file looks like this: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-release-plugin</artifactId> <configuration> <autoVersionSubmodules>true</autoVersionSubmodules> <checkModificationExcludes> <checkModificationExclude>pom.xml</checkModificationExclude> </checkModificationExcludes> </configuration> </plugin> However, it is still complaining that the pom.xml file is modified (it is). If I run the prepare goal with debug on, this is the configuration that is displayed: [DEBUG] Goal: org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) [DEBUG] Style: Aggregating [DEBUG] Configuration: <?xml version="1.0" encoding="UTF-8"?> <configuration> <addSchema default-value="true">${addSchema}</addSchema> <allowReleasePluginSnapshot default-value="false">${allowReleasePluginSnapshot}</allowReleasePluginSnapshot> <allowTimestampedSnapshots default-value="false">${ignoreSnapshots}</allowTimestampedSnapshots> <arguments>${arguments}</arguments> <autoVersionSubmodules default-value="false">true</autoVersionSubmodules> <basedir>${basedir}</basedir> <commitByProject default-value="false">${commitByProject}</commitByProject> <developmentVersion>${developmentVersion}</developmentVersion> <dryRun default-value="false">${dryRun}</dryRun> <generateReleasePoms default-value="false">${generateReleasePoms}</generateReleasePoms> <javaHome default-value="${java.home}"/> <localCheckout default-value="false">${localCheckout}</localCheckout> <localRepoDirectory default-value="${maven.repo.local}"/> <mavenExecutorId default-value="invoker">${mavenExecutorId}</mavenExecutorId> <mavenHome default-value="${maven.home}"/> <password>${password}</password> <pomFileName>${pomFileName}</pomFileName> <preparationGoals default-value="clean verify">${preparationGoals}</preparationGoals> <project>${project}</project> <reactorProjects>${reactorProjects}</reactorProjects> <releaseVersion>${releaseVersion}</releaseVersion> <remoteTagging default-value="true">${remoteTagging}</remoteTagging> <resume default-value="true">${resume}</resume> <scmCommentPrefix default-value="[maven-release-plugin] ">${scmCommentPrefix}</scmCommentPrefix> <session>${session}</session> <settings>${settings}</settings> <tag>${tag}</tag> <tagBase>${tagBase}</tagBase> <updateDependencies default-value="true">${updateDependencies}</updateDependencies> <useEditMode default-value="false">${useEditMode}</useEditMode> <username>${username}</username> </configuration> [DEBUG] ======================================================================= And later on [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-release-plugin:2.0:prepare' with basic configurator --> [DEBUG] (f) addSchema = true [DEBUG] (f) allowReleasePluginSnapshot = false [DEBUG] (f) allowTimestampedSnapshots = false [DEBUG] (f) autoVersionSubmodules = true [DEBUG] (s) basedir = <snip> [DEBUG] (f) commitByProject = false [DEBUG] (f) dryRun = true [DEBUG] (f) generateReleasePoms = false [DEBUG] (f) javaHome = C:\Program Files\Java\jdk1.6.0_29\jre [DEBUG] (f) localCheckout = false [DEBUG] (f) mavenExecutorId = invoker [DEBUG] (f) mavenHome = C:\sbox\trunk\tools\bin\apache-maven-3.0.3 [DEBUG] (f) preparationGoals = clean verify [DEBUG] (f) project = <snip> [DEBUG] (f) reactorProjects = <snip> [DEBUG] (f) remoteTagging = true [DEBUG] (f) resume = true [DEBUG] (f) scmCommentPrefix = [maven-release-plugin] [DEBUG] (f) session = org.apache.maven.execution.MavenSession@17496e57 [DEBUG] (f) settings = org.apache.maven.execution.SettingsAdapter@3eeabd2f [DEBUG] (f) updateDependencies = true [DEBUG] (f) useEditMode = false [DEBUG] -- end configuration -- [INFO] Resuming release from phase 'scm-check-modifications' [INFO] Verifying that there are no local modifications... [INFO] Executing: cmd.exe /X /C "svn --non-interactive status" [INFO] Working directory: <snip> [DEBUG] ? release.properties [DEBUG] M pom.xml I guess I was expecting some mention in the debug of the checkModificationExcludes settings, but there's none? Has anyone been using this in version 2.2.2? Thanks for any help, Ed