[
http://jira.codehaus.org/browse/MNG-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4020:
-----------------------------------
Description:
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
was:
I have a scenario where the SCM tag is configured with the following:
<scm>
<connection>scm:perforce:p4server:1666://components/projectA/pom.xml</connection>
<developerConnection>scm:perforce:p4server:1666://components/projectA/pom.xml</developerConnection>
</scm>
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
> Release plugin disregards SCM configured element within the pom
> ---------------------------------------------------------------
>
> Key: MNG-4020
> URL: http://jira.codehaus.org/browse/MNG-4020
> Project: Maven 2
> 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
>
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
