Hi Michael,

>> I use it (with Mercurial 4.5.3), both with the maven-release-plugin and
>> for some basic operations like scm:tag in scripts (although that would
>> be easily replaceable with a direct invocation).
> 
> Any reason why you are not on 5.x? I don't even know what changes were
> introduced in 5.0 which do not properly work with Maven SCM.

no reason in particular. It's just the version that ships with Ubuntu
18.4 LTS version I am using.

But I would not expect the Maven SCM developers to test against older
Mercurial versions. Hence, just testing against 5.x is fine by me.

That being said, from a Maven SCM standpoint, I would not expect to see
any breakage with Mercurial 4.x give that Maven just forks the Mercurial
process and parses results. AFAICT, this interface is kept very stable
by the Mercurial team precisely because a lot of people use Mercurial
like that in their scripts. If Maven SCM would use, say, Jython to
access Mercurial internals directly in the JVM process, things would, of
course, be different, but you don't and should hence be quite safe.

Hope that helps.

Best wishes,

Andreas

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to