Am 14.12.2009 um 13:08 schrieb Mark Struberg:
> the <scm> element in the pom is used for every SCM action in maven, e.g. if
> you do a mvn release:prepare / mvn release:perform and stuff.
>
> Since Hudson and other CI environments often do not rely on the build system
> for updating the project, they have the ability to do this their self (otoh,
> some CI systems do use maven-scm internally, but get the scm URL parameter
> from the UI rather than the pom.
Hm, just lately I tried the following with a project in Subversion:
- Checked out a project from trunk
<scm>
<connection>scm:svn:file:///Software/nobackup/svn/myproject/branches/stable</connection>
<developerConnection>scm:svn:file:///Software/nobackup/svn/myproject/branches/stable</developerConnection>
</scm>
<build>
<plugins>
<plugin>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<tagBase>file:///Software/nobackup/svn/myproject/releases</tagBase>
</configuration>
</plugin>
- Both developerConnection and connection in the pom point to branches/stable
- My goal was to have releases built from this stable branch and tags landing
under releases.
- When I issued "mvn release:prepare" from the trunk checkout not the
branches/stable version was released but the (trunk) working copy was copied to
releases.
Best Regards
Mirko
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
