I tried to release Studio 104 yesterday. I ran mvn release:prepare and it made a branch using svn copy. A problem was that it used a bad SCM path in pom.xml, which came from an old branch merge.

trunk's pom.xml had:

<scm>
    <connection>scm:svn:https://studio.atlassian.com/svn/JST/branches/studio-streams4-upgrade</connection>
    <developerConnection>scm:svn:https://studio.atlassian.com/svn/JST/branches/studio-streams4-upgrade</developerConnection>
    <url>https://studio.atlassian.com/svn/JST/branches/studio-streams4-upgrade</url>
</scm>

Notice that it's pointing to studio-streams4-upgrade (from a prior merge). It should have been:

<scm>
    <connection>scm:svn:https://studio.atlassian.com/svn/JST/trunk</connection>
    <developerConnection>scm:svn:https://studio.atlassian.com/svn/JST/trunk</developerConnection>
    <url>https://studio.atlassian.com/svn/JST/trunk</url>
</scm>

We should create some type of check for this. Ashwin pointed out that JST-DEPS already does some validation for trunk and we should be able to extend it to the <scm> element.

It took a lot of time to track down this problem and to fix it. I had to rollback the changes, put code freeze back in place, fix up the SCM path and do the release again. Felipe, Sam H and Alex all mentioned that this problem has happened before. Putting this check in place might make releases smoother.