Hello Robert,
it's quite long ago that you answered my initial question, and I have been
pretty busy with my $DAYJOB, but I wanted to say thanks for the pointers you
gave.
Using these hints I finally figured out how to realize such a feature and
just added a quite simple patch to the Maven SCM pl
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 e
Op Thu, 17 Dec 2015 12:31:02 +0100 schreef Thorsten Heit
:
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 (
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 a
