What about perforce or clearcase ?
-Original Message-
From: Mark Struberg [mailto:strub...@yahoo.de]
Sent: Sunday, March 06, 2011 4:40 PM
To: Maven Users List
Subject: Re: How to release a single module in a Mercurial repository?
hmm, I think we should remove this Exception.
tagging a sub
hmm, I think we should remove this Exception.
tagging a subdirectory is again only valid in very special SCMs, mainly SVN
(don't remember how this did behave in CVS anymore).
Usually a tag is a 'name' on a certain snapshot in the whole repo. Tagging a
repo will just give you this unique snapsh
Hi,
I've attached my hg repository that I used for testing to the above
mentioned jira issue.
As I have written in my email, the *only* way I could make the release
plugin work for releasing a submodule was to copy the scm information into
each an every module. While this may work, and with your
Hi Oliverm
2011/3/5 Olivier Lamy
> @Andreas
>
> I see you are using scm 1.4
>
>
> org.apache.maven.scm
> maven-scm-provider-hg
> 1.4
>
>
> Can you try with 1.5-SNAPSHOT ?
>
Yes, I am using the 1.4 release, because the 1.5-Snapshot gave an error
message, that it cannot tag subdirectorie
Using maven enforcer plugin, how can I ensure that all projects are using a
a plugin version >= than the one I defined?
For example, I want to ensure all the projects in the company (we use a
company super pom) use maven release plugin >= 2.1 version
In the company super pom we are using pluginMa
hmm, looks good so far. The only thing I noticed is that the URL in the child
module doesn't contain a trailing /:
scm:hg:https://maven-scm-provider-hg-test.googlecode.com/hg
vs
scm:hg:https://maven-scm-provider-hg-test.googlecode.com/hg/
does this make any difference? (Shouldn't but I've seen
