For the maven-release-plugin and maven-scm this is not possible.
I can give you a couple of links which you can look at to understand
what's happening right now.
Keep in mind that if we want to add such feature, we need to think for all
SCMs, and not just svn.
If there are more SCMs with an equivalent option (not sure if there is
one), we should bundle them and think of the proper approach.
Here's where the commandline in constructed:
http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/xref/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.html
Here we probably need an extra field...
http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/xref/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.html
Here's where the information of the maven-release-plugin is passed through
to the SCM Provider
http://maven.apache.org/components/maven-release/maven-release-manager/xref/org/apache/maven/shared/release/phase/ScmTagPhase.html
I've seen more request asking for svn externals, but there wasn't a really
good way to implement this. Maybe with svn 1.9 there is.
thanks,
Robert
Op Thu, 17 Dec 2015 12:31:02 +0100 schreef Thorsten Heit
<[email protected]>:
Hi,
I have a few Maven projects that use svn:externals to link to code and/or
resources stored in different paths in our Subversion repository.
Compiling, packaging, deploying etc, works fine; even creating releases
with m-release-p (release:prepare && release:perform).
The svn:externals I'm actually using refer to files / folders in the
trunk, not fixed versions. Example:
^/trunk/projectA/fileA fileA
Therefore, when you check out a tagged release created with m-release-p
somewhere in the future, the checked out files could be different
compared
to the time the release was created. To prevent this, I'm actually
manually changing the svn:externals definition in the tagged release to
reference fixed versions of the desired files/folders after m-release-p
is
finished:
-r<rev> ^/trunk/projectA/fileA fileA
Is there a way to automate this?
According to the release notes of Subversion 1.9, there's a new option
"--pin-externals" available for "svn copy". Is it possible to use that?
If
yes, how can I do this?
I've also found this plugin here:
https://github.com/MartinMReed/maven-svn-plugin
What do you think?
Regards
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
