maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Ebbert-Karroum (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (SCM-612) maven-release-plugin causes mercurial scm provider to fail when only a module is released
Date Tue, 29 Nov 2011 18:59:39 GMT

    [ https://jira.codehaus.org/browse/SCM-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284536#comment-284536
] 

Andreas Ebbert-Karroum commented on SCM-612:
--------------------------------------------

Hi,

any progress on this? I'm still unable to release mercurial projects with maven :(

Andreas

> maven-release-plugin causes mercurial scm provider to fail when only a module is released
> -----------------------------------------------------------------------------------------
>
>                 Key: SCM-612
>                 URL: https://jira.codehaus.org/browse/SCM-612
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-mercurial (hg)
>    Affects Versions: 1.4, 1.5
>            Reporter: Andreas Ebbert-Karroum
>            Assignee: Olivier Lamy
>         Attachments: hg-repo.zip
>
>
> Problem as described on the [maven-users mailing list|http://maven.40175.n5.nabble.com/How-to-release-a-single-module-in-a-Mercurial-repository-tp3406421p3406421.html].
Basically it is not possible to release a single module from a multi-module project with mercurial
as scm provider.
> h2. When trying with current 1.5-SNAPSHOT:
> {code}
> Caused by: org.apache.maven.scm.ScmException: This provider doesn't support tagging subsets
of a directory
>         at org.apache.maven.scm.provider.hg.command.tag.HgTagCommand.executeTagCommand(HgTagCommand.java:77)
>         at org.apache.maven.scm.command.tag.AbstractTagCommand.executeCommand(AbstractTagCommand.java:81)
>         at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
>         ... 29 more 
> {code}
> h2. When trying with 1.4 release
> It is more complicated, but also does not work. It boils down to having a mandatory pom.xml
in the repository root and scm url messed up during the release:prepare and release:perform
phases. See mentioned email for more details.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message