[
https://issues.apache.org/jira/browse/MRELEASE-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992005#comment-14992005
]
(d) Lincoln Baxter III commented on MRELEASE-878:
-------------------------------------------------
Using 'checkModificationExcludes" seems to work around the issue:
{code}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.5.3</version>
<configuration>
<checkModificationExcludes>
<checkModificationExclude>dependency-reduced-pom.xml</checkModificationExclude>
</checkModificationExcludes>
</configuration>
</plugin>
</plugins>
{code}
> Exclude generated dependency-reduced-pom.xml and flattened-pom.xml
> ------------------------------------------------------------------
>
> Key: MRELEASE-878
> URL: https://issues.apache.org/jira/browse/MRELEASE-878
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.5
> Reporter: Mirko Friedenhagen
>
> As stated in MOJO-2030 and MSHADE-145, both plugins create additional poms in
> {{basedir}} to avoid confusion while generating the site.
> This will lead to an error during {{release:prepare}}, so just exclude
> {{dependency-reduced-pom.xml}} and {{flattened-pom.xml}} by default as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
