have definition
in you modules' -tags.
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-release-plugin-and-subversion-externals-tp109483p5710914.html
Sent from the Maven - Users mailing list archive at
tag", I just feel in
this context word "branch" better describes what we are doing (and in svn
there is no tag or branch, just copy).
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-release-p
Yours Rüdiger
--
View this message in context:
http://n2.nabble.com/maven-release-plugin-and-subversion-externals-tp4514253p4519649.html
Sent from the maven users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail:
Hi,
we are referencing the trunk of the modules without a revision
http://svn/repo/module1/trunk module1
http://svn/repo/module2/trunk module2
This brings me to the question:
Why not putting all modules in the folder structure
Root
+--- module1
+--- module2
without using sv
Hi,
We are calling: mvn release.clean release:prepare release:perform
and there are no error messages.
If you do an mvn release:perform ...aren't you asked for the release
version etc. during the process ?
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +4
runk with a particular revision ?
> ...
>
we are referencing the trunk of the modules without a revision
http://svn/repo/module1/trunk module1
http://svn/repo/module2/trunk module2
Yours Rüdiger
--
View this message in context:
http://n2.nabble.com/maven-release-plugin-and-subvers
Hi there
first: Have you defined scm section in your root pom ?
we are using svn:externals to add our modules into the parent directory.
We can build, test, deploy ... but we can't create a release. The release is
only
How do you use the externals ? fixed to a particular release via tag
name
e.com/maven-release-plugin-and-subversion-externals-tp4514253p4514253.html
Sent from the maven users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-ma
