Hi, When I use TeamCity Artifactory Plugin Release to make a release build, it copies the sources to the tags directory and updates the <scm> part in the pom.xml, which is nice. However, after a release is done, the <scm> path still points to the "tags":
Before release: <scm> <connection>scm:svn:http://svn.server/repos/myproject/trunk</connection> <developerConnection>http://svn.server/repos/myproject/trunk</developerConnection> <url>http://svn.server/repos/myproject/trunk</url> </scm> After release: <scm> <connection>scm:svn:http://svn.server/repos/myproject/tags/1.0.0-parent</connection> <developerConnection>http://svn.server/repos/myproject/tags/1.0.0-parent</developerConnection> <url>http://svn.server/repos/myproject/tags/1.0.0-parent</url> </scm> If I make a release using "mvn release:prepare release:perform --batch-mode", it will automatically put back the path to the trunk one. Any ideas why the plugin does not do the same way as Maven does? Is there any way I configure this behavior? Thanks. -- View this message in context: http://forums.jfrog.org/TeamCity-Artifactory-Plugin-Release-tp7579494.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
