I've added my own Maven plug-in to the build process like that:

```
    <plugins>
        <plugin>
            <artifactId>maven-release-plugin</artifactId>
            <configuration>
                <tagBase>...</tagBase>
                <preparationGoals>clean verify org.acme:my-super-cool-plugin:the-goal</preparationGoals>
                <completionGoals>org.acme:my-super-cool-plugin:the-goal"</completionGoals>
            </configuration>
        </plugin>
    </plugins>

    <pluginManagement>
        <plugins>
            <plugin>
                <groupId>org.acme</groupId>
                <artifactId>my-super-cool-plugin</artifactId>
                <version>1.2.3</version>
                <executions>
                    <execution>
                        <id>my-super-cool-id</id>
                        <phase>validate</phase>
                        <goals>
                            <goal>the-goal</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </pluginManagement>

```

Now the [documentation](http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#completionGoals) states that `completionGoals` is called "after transformation back to the next development version but before committing", yet after releasing I see the changes my plug-in made as local changes only, they were not commited.

I already "fixed" it by adding `scm:checkin` to the `completionGoals` tag, but I'm wondering why it's not commited on it's own. Could it be because it's a Tycho project and that's screwing the Maven lifecycle up?