maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Closed: (MRELEASE-411) Release plugin disregards SCM configured element within the pom
Date Sat, 18 Sep 2010 03:34:32 GMT


Brett Porter closed MRELEASE-411.

    Resolution: Won't Fix
      Assignee: Brett Porter

This is not how the SCM element is designed to work in Maven, so the release plugin can't
support it.

You could make a feature request to support shallow checkouts by the release plugin, however
I'd encourage you to structure the project so that release units are self contained.

> Release plugin disregards SCM configured element within the pom
> ---------------------------------------------------------------
>                 Key: MRELEASE-411
>                 URL:
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: perform
>    Affects Versions: 2.0-beta-7
>         Environment: Maven 2.0.9 using maven-release-plugin version 2.0-beta-7
>            Reporter: Robert Bracewell
>            Assignee: Brett Porter
> I have a scenario where the SCM tag is configured with the following:
> {code:xml}
> <scm>
>   <connection>scm:perforce:p4server:1666://components/projectA/pom.xml</connection>
>   <developerConnection>scm:perforce:p4server:1666://components/projectA/pom.xml</developerConnection>
> </scm>
> {code}
> The location in Perforce //components/projectA contains the pom.xml in question and then
a bunch of sub-directories located at the same level as the pom.
> When the release plugin runs a perform it churns out the following:
> [INFO] [release:perform]
> [INFO] Checking out the project to perform the release ...
> [INFO] The SCM location in your pom.xml (//components/projectA/pom.xml) is not equal
to the depot location (//components/projectA).  This happens frequently with branches.  Ignoring
the SCM location.
> For my situation the above is incorrect as I am only releasing a pom not several modules.
The release:perform then continues to sync every file located under //components/projectA
which in my case is several thousand and as such takes several minutes to complete.
> The release plugin should be able to handle such SCM elements and understand that only
a single file is being released when such is explicitly defined

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message