You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Chris Graham <ch...@gmail.com> on 2012/05/15 12:10:32 UTC
Change of behavior with the SCM/Release Plugin?
Hi All.
I'm reasonably sure that I tested the release process with jazz scm/release
plugin several times, over and over.
Running the command:
mvn -B -Dresume=false -DignoreSnapshots=true
-DworkingDirectory=C:\tmp\maven release:prepare release:perform
followed immediately again with the same command.
But I've now noticed that I now get an error:
C:\CALMData\Workspaces\RTC\Deb\GPDB>mvn -B -Dresume=false
-DignoreSnapshots=true -DworkingDirectory=C:\tmp\maven release:prepare
release:perform
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] GPDB - J2EE Multi Module Project
[INFO] GPDB - Resources Project
[INFO] GPDB - WAR Project
[INFO] GPDB - EAR Project
[INFO]
------------------------------------------------------------------------
[INFO] Building GPDB - J2EE Multi Module Project
[INFO] task-segment: [release:prepare, release:perform]
(aggregator-style)
[INFO]
------------------------------------------------------------------------
[INFO] [release:prepare {execution: default-cli}]
[INFO] Verifying that there are no local modifications...
[INFO] ignoring changes on: **\pom.xml.branch, **\pom.xml.backup,
**\pom.xml.releaseBackup, **\release.properties, **\pom.xml.next,
**\pom.xml.tag
[INFO] Executing: cmd.exe /X /C "scm status --username Deb --password *****
--wide"
[INFO] Working directory: C:\CALMData\Workspaces\RTC\Deb\GPDB
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Cannot prepare the release because you have local modifications :
[/GPDB/release.properties:added]
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 24 seconds
[INFO] Finished at: Tue May 15 20:07:09 EST 2012
[INFO] Final Memory: 24M/81M
[INFO]
------------------------------------------------------------------------
C:\CALMData\Workspaces\RTC\Deb\GPDB>
Has anything changed? This is after a release:clean.
-Chris
Re: Change of behavior with the SCM/Release Plugin?
Posted by Robert Scholte <ap...@sourcegrounds.com>.
hi Chris,
My first impression would be that you hit a problem with the improvement
thanks to MRELEASE-645[1]
I notice a different file-separator, although I though I'd covered that.
The issue has links to the adjustments.
I have to check it this is indeed the problem.
Robert
[1] https://jira.codehaus.org/browse/MRELEASE-645
Op Tue, 15 May 2012 12:10:32 +0200 schreef Chris Graham
<ch...@gmail.com>:
> Hi All.
>
> I'm reasonably sure that I tested the release process with jazz
> scm/release
> plugin several times, over and over.
>
> Running the command:
> mvn -B -Dresume=false -DignoreSnapshots=true
> -DworkingDirectory=C:\tmp\maven release:prepare release:perform
>
> followed immediately again with the same command.
>
> But I've now noticed that I now get an error:
>
> C:\CALMData\Workspaces\RTC\Deb\GPDB>mvn -B -Dresume=false
> -DignoreSnapshots=true -DworkingDirectory=C:\tmp\maven release:prepare
> release:perform
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] GPDB - J2EE Multi Module Project
> [INFO] GPDB - Resources Project
> [INFO] GPDB - WAR Project
> [INFO] GPDB - EAR Project
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building GPDB - J2EE Multi Module Project
> [INFO] task-segment: [release:prepare, release:perform]
> (aggregator-style)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [release:prepare {execution: default-cli}]
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: **\pom.xml.branch, **\pom.xml.backup,
> **\pom.xml.releaseBackup, **\release.properties, **\pom.xml.next,
> **\pom.xml.tag
> [INFO] Executing: cmd.exe /X /C "scm status --username Deb --password
> *****
> --wide"
> [INFO] Working directory: C:\CALMData\Workspaces\RTC\Deb\GPDB
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Cannot prepare the release because you have local modifications :
> [/GPDB/release.properties:added]
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 24 seconds
> [INFO] Finished at: Tue May 15 20:07:09 EST 2012
> [INFO] Final Memory: 24M/81M
> [INFO]
> ------------------------------------------------------------------------
> C:\CALMData\Workspaces\RTC\Deb\GPDB>
>
> Has anything changed? This is after a release:clean.
>
> -Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Change of behavior with the SCM/Release Plugin?
Posted by Robert Scholte <ap...@sourcegrounds.com>.
Hi Chris,
I've added
org.apache.maven.scm.provider.jazz.command.status.JazzStatusConsumerTest,
which contains a test which should succeed according the restrictions due
to SCM-674 [1]
I don't know if Jazz will keep the starting slash, or if we can assume
it'll always start with it (so we can always remove the first char of the
path).
Based on that answer we can work on the adjustment.
-Robert
[1] https://jira.codehaus.org/browse/SCM-674
Op Thu, 17 May 2012 11:03:58 +0200 schreef Robert Scholte
<ap...@sourcegrounds.com>:
> The workaround for you is probably:
> <checkModificationExcludes>
> <checkModificationExclude>/**/pom.xml.branch<checkModificationExclude>
> <checkModificationExclude>/**/pom.xml.backup<checkModificationExclude>
> <checkModificationExclude>/**/pom.xml.releaseBackup<checkModificationExclude>
> <checkModificationExclude>/**/release.properties<checkModificationExclude>
> <checkModificationExclude>/**/pom.xml.next<checkModificationExclude>
> <checkModificationExclude>/**/pom.xml.tag<checkModificationExclude>
> </checkModificationExcludes>
>
> -Robert
>
>
> Op Thu, 17 May 2012 02:12:02 +0200 schreef Chris Graham
> <ch...@gmail.com>:
>
>> Is there any way that we can supply our own spec?
>>
>> [INFO] ignoring changes on: **\pom.xml.branch, **\pom.xml.backup,
>> **\pom.xml.releaseBackup, **\release.properties, **\pom.xml.next,
>> **\pom.xml.tag
>>
>> Then I could adjust it as necessary.
>>
>> Are these properties exposed?
>>
>> -Chris
>>
>> On Thu, May 17, 2012 at 2:49 AM, Robert Scholte
>> <ap...@sourcegrounds.com>wrote:
>>
>>> The implementation up until 2.2.2 did an endsWith()-match, but this
>>> made
>>> it impossible to exclude a specific file.
>>> The pinpoint the real problem check the first lines of the
>>> SelectorUtils#*
>>> *matchAntPathPatternStart [1]
>>> For NON-Windows OS this is correct, but with Windows you can have your
>>> doubts.
>>>
>>> -Robert
>>>
>>> [1] http://plexus.codehaus.org/**plexus-utils/xref/org/**
>>> codehaus/plexus/util/**SelectorUtils.html#171<http://plexus.codehaus.org/plexus-utils/xref/org/codehaus/plexus/util/SelectorUtils.html#171>
>>>
>>> Op Wed, 16 May 2012 03:59:56 +0200 schreef Chris Graham <
>>> chrisgwarp@gmail.com>:
>>>
>>> Which leaves me with the question: Given the 100's of releases that I
>>> ran,
>>>> why did it rear it's ugly head now?
>>>>
>>>> The leading slash has always been there.
>>>>
>>>> I've got a work around in place. I run "mvn release:clean" and then
>>>> manually delete the properties file.
>>>>
>>>> There may also be some interactions with the underlying eclipse
>>>> workspace.
>>>>
>>>> It's wierd.
>>>>
>>>> If I manually delete the files, and re-run it fails.
>>>>
>>>> If I delete the files in the eclipse client (which refreshes the
>>>> workspace)
>>>> and then re-run, it works.
>>>>
>>>> It's really odd.
>>>>
>>>> But, I can get releases out, and that is the most important bit.
>>>>
>>>> -Chris
>>>>
>>>> On Wed, May 16, 2012 at 4:38 AM, Robert Scholte
>>>> <apache@sourcegrounds.com
>>>> >**wrote:
>>>>
>>>> Hi Chris,
>>>>>
>>>>> it's the starting slash which causes trouble:
>>>>> /GPDB/release.properties
>>>>>
>>>>> It think that we should try to solve this in the SCM-project, so all
>>>>> files
>>>>> are handled the same, no matter the scm-provider
>>>>>
>>>>> -Robert
>>>>>
>>>>>
>>>>> Op Tue, 15 May 2012 12:10:32 +0200 schreef Chris Graham <
>>>>> chrisgwarp@gmail.com>:
>>>>>
>>>>> Hi All.
>>>>>
>>>>>>
>>>>>> I'm reasonably sure that I tested the release process with jazz
>>>>>> scm/release
>>>>>> plugin several times, over and over.
>>>>>>
>>>>>> Running the command:
>>>>>> mvn -B -Dresume=false -DignoreSnapshots=true
>>>>>> -DworkingDirectory=C:\tmp\****maven release:prepare release:perform
>>>>>>
>>>>>>
>>>>>> followed immediately again with the same command.
>>>>>>
>>>>>> But I've now noticed that I now get an error:
>>>>>>
>>>>>> C:\CALMData\Workspaces\RTC\****Deb\GPDB>mvn -B -Dresume=false
>>>>>> -DignoreSnapshots=true -DworkingDirectory=C:\tmp\****maven
>>>>>> release:prepare
>>>>>>
>>>>>> release:perform
>>>>>> [INFO] Scanning for projects...
>>>>>> [INFO] Reactor build order:
>>>>>> [INFO] GPDB - J2EE Multi Module Project
>>>>>> [INFO] GPDB - Resources Project
>>>>>> [INFO] GPDB - WAR Project
>>>>>> [INFO] GPDB - EAR Project
>>>>>> [INFO]
>>>>>> ------------------------------****----------------------------**--**
>>>>>>
>>>>>> ------------
>>>>>> [INFO] Building GPDB - J2EE Multi Module Project
>>>>>> [INFO] task-segment: [release:prepare, release:perform]
>>>>>> (aggregator-style)
>>>>>> [INFO]
>>>>>> ------------------------------****----------------------------**--**
>>>>>>
>>>>>> ------------
>>>>>> [INFO] [release:prepare {execution: default-cli}]
>>>>>> [INFO] Verifying that there are no local modifications...
>>>>>> [INFO] ignoring changes on: **\pom.xml.branch, **\pom.xml.backup,
>>>>>> **\pom.xml.releaseBackup, **\release.properties, **\pom.xml.next,
>>>>>> **\pom.xml.tag
>>>>>> [INFO] Executing: cmd.exe /X /C "scm status --username Deb
>>>>>> --password
>>>>>> *****
>>>>>> --wide"
>>>>>> [INFO] Working directory: C:\CALMData\Workspaces\RTC\****Deb\GPDB
>>>>>> [INFO]
>>>>>> ------------------------------****----------------------------**--**
>>>>>> ------------
>>>>>> [ERROR] BUILD FAILURE
>>>>>> [INFO]
>>>>>> ------------------------------****----------------------------**--**
>>>>>>
>>>>>> ------------
>>>>>> [INFO] Cannot prepare the release because you have local
>>>>>> modifications :
>>>>>> [/GPDB/release.properties:****added]
>>>>>>
>>>>>> [INFO]
>>>>>> ------------------------------****----------------------------**--**
>>>>>>
>>>>>> ------------
>>>>>> [INFO] For more information, run Maven with the -e switch
>>>>>> [INFO]
>>>>>> ------------------------------****----------------------------**--**
>>>>>>
>>>>>> ------------
>>>>>> [INFO] Total time: 24 seconds
>>>>>> [INFO] Finished at: Tue May 15 20:07:09 EST 2012
>>>>>> [INFO] Final Memory: 24M/81M
>>>>>> [INFO]
>>>>>> ------------------------------****----------------------------**--**
>>>>>> ------------
>>>>>> C:\CALMData\Workspaces\RTC\****Deb\GPDB>
>>>>>>
>>>>>>
>>>>>> Has anything changed? This is after a release:clean.
>>>>>>
>>>>>> -Chris
>>>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Change of behavior with the SCM/Release Plugin?
Posted by Robert Scholte <ap...@sourcegrounds.com>.
The workaround for you is probably:
<checkModificationExcludes>
<checkModificationExclude>/**/pom.xml.branch<checkModificationExclude>
<checkModificationExclude>/**/pom.xml.backup<checkModificationExclude>
<checkModificationExclude>/**/pom.xml.releaseBackup<checkModificationExclude>
<checkModificationExclude>/**/release.properties<checkModificationExclude>
<checkModificationExclude>/**/pom.xml.next<checkModificationExclude>
<checkModificationExclude>/**/pom.xml.tag<checkModificationExclude>
</checkModificationExcludes>
-Robert
Op Thu, 17 May 2012 02:12:02 +0200 schreef Chris Graham
<ch...@gmail.com>:
> Is there any way that we can supply our own spec?
>
> [INFO] ignoring changes on: **\pom.xml.branch, **\pom.xml.backup,
> **\pom.xml.releaseBackup, **\release.properties, **\pom.xml.next,
> **\pom.xml.tag
>
> Then I could adjust it as necessary.
>
> Are these properties exposed?
>
> -Chris
>
> On Thu, May 17, 2012 at 2:49 AM, Robert Scholte
> <ap...@sourcegrounds.com>wrote:
>
>> The implementation up until 2.2.2 did an endsWith()-match, but this made
>> it impossible to exclude a specific file.
>> The pinpoint the real problem check the first lines of the
>> SelectorUtils#*
>> *matchAntPathPatternStart [1]
>> For NON-Windows OS this is correct, but with Windows you can have your
>> doubts.
>>
>> -Robert
>>
>> [1] http://plexus.codehaus.org/**plexus-utils/xref/org/**
>> codehaus/plexus/util/**SelectorUtils.html#171<http://plexus.codehaus.org/plexus-utils/xref/org/codehaus/plexus/util/SelectorUtils.html#171>
>>
>> Op Wed, 16 May 2012 03:59:56 +0200 schreef Chris Graham <
>> chrisgwarp@gmail.com>:
>>
>> Which leaves me with the question: Given the 100's of releases that I
>> ran,
>>> why did it rear it's ugly head now?
>>>
>>> The leading slash has always been there.
>>>
>>> I've got a work around in place. I run "mvn release:clean" and then
>>> manually delete the properties file.
>>>
>>> There may also be some interactions with the underlying eclipse
>>> workspace.
>>>
>>> It's wierd.
>>>
>>> If I manually delete the files, and re-run it fails.
>>>
>>> If I delete the files in the eclipse client (which refreshes the
>>> workspace)
>>> and then re-run, it works.
>>>
>>> It's really odd.
>>>
>>> But, I can get releases out, and that is the most important bit.
>>>
>>> -Chris
>>>
>>> On Wed, May 16, 2012 at 4:38 AM, Robert Scholte
>>> <apache@sourcegrounds.com
>>> >**wrote:
>>>
>>> Hi Chris,
>>>>
>>>> it's the starting slash which causes trouble:
>>>> /GPDB/release.properties
>>>>
>>>> It think that we should try to solve this in the SCM-project, so all
>>>> files
>>>> are handled the same, no matter the scm-provider
>>>>
>>>> -Robert
>>>>
>>>>
>>>> Op Tue, 15 May 2012 12:10:32 +0200 schreef Chris Graham <
>>>> chrisgwarp@gmail.com>:
>>>>
>>>> Hi All.
>>>>
>>>>>
>>>>> I'm reasonably sure that I tested the release process with jazz
>>>>> scm/release
>>>>> plugin several times, over and over.
>>>>>
>>>>> Running the command:
>>>>> mvn -B -Dresume=false -DignoreSnapshots=true
>>>>> -DworkingDirectory=C:\tmp\****maven release:prepare release:perform
>>>>>
>>>>>
>>>>> followed immediately again with the same command.
>>>>>
>>>>> But I've now noticed that I now get an error:
>>>>>
>>>>> C:\CALMData\Workspaces\RTC\****Deb\GPDB>mvn -B -Dresume=false
>>>>> -DignoreSnapshots=true -DworkingDirectory=C:\tmp\****maven
>>>>> release:prepare
>>>>>
>>>>> release:perform
>>>>> [INFO] Scanning for projects...
>>>>> [INFO] Reactor build order:
>>>>> [INFO] GPDB - J2EE Multi Module Project
>>>>> [INFO] GPDB - Resources Project
>>>>> [INFO] GPDB - WAR Project
>>>>> [INFO] GPDB - EAR Project
>>>>> [INFO]
>>>>> ------------------------------****----------------------------**--**
>>>>>
>>>>> ------------
>>>>> [INFO] Building GPDB - J2EE Multi Module Project
>>>>> [INFO] task-segment: [release:prepare, release:perform]
>>>>> (aggregator-style)
>>>>> [INFO]
>>>>> ------------------------------****----------------------------**--**
>>>>>
>>>>> ------------
>>>>> [INFO] [release:prepare {execution: default-cli}]
>>>>> [INFO] Verifying that there are no local modifications...
>>>>> [INFO] ignoring changes on: **\pom.xml.branch, **\pom.xml.backup,
>>>>> **\pom.xml.releaseBackup, **\release.properties, **\pom.xml.next,
>>>>> **\pom.xml.tag
>>>>> [INFO] Executing: cmd.exe /X /C "scm status --username Deb --password
>>>>> *****
>>>>> --wide"
>>>>> [INFO] Working directory: C:\CALMData\Workspaces\RTC\****Deb\GPDB
>>>>> [INFO]
>>>>> ------------------------------****----------------------------**--**
>>>>> ------------
>>>>> [ERROR] BUILD FAILURE
>>>>> [INFO]
>>>>> ------------------------------****----------------------------**--**
>>>>>
>>>>> ------------
>>>>> [INFO] Cannot prepare the release because you have local
>>>>> modifications :
>>>>> [/GPDB/release.properties:****added]
>>>>>
>>>>> [INFO]
>>>>> ------------------------------****----------------------------**--**
>>>>>
>>>>> ------------
>>>>> [INFO] For more information, run Maven with the -e switch
>>>>> [INFO]
>>>>> ------------------------------****----------------------------**--**
>>>>>
>>>>> ------------
>>>>> [INFO] Total time: 24 seconds
>>>>> [INFO] Finished at: Tue May 15 20:07:09 EST 2012
>>>>> [INFO] Final Memory: 24M/81M
>>>>> [INFO]
>>>>> ------------------------------****----------------------------**--**
>>>>> ------------
>>>>> C:\CALMData\Workspaces\RTC\****Deb\GPDB>
>>>>>
>>>>>
>>>>> Has anything changed? This is after a release:clean.
>>>>>
>>>>> -Chris
>>>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Change of behavior with the SCM/Release Plugin?
Posted by Robert Scholte <ap...@sourcegrounds.com>.
Hi Chris,
it's the starting slash which causes trouble:
/GPDB/release.properties
It think that we should try to solve this in the SCM-project, so all files
are handled the same, no matter the scm-provider
-Robert
Op Tue, 15 May 2012 12:10:32 +0200 schreef Chris Graham
<ch...@gmail.com>:
> Hi All.
>
> I'm reasonably sure that I tested the release process with jazz
> scm/release
> plugin several times, over and over.
>
> Running the command:
> mvn -B -Dresume=false -DignoreSnapshots=true
> -DworkingDirectory=C:\tmp\maven release:prepare release:perform
>
> followed immediately again with the same command.
>
> But I've now noticed that I now get an error:
>
> C:\CALMData\Workspaces\RTC\Deb\GPDB>mvn -B -Dresume=false
> -DignoreSnapshots=true -DworkingDirectory=C:\tmp\maven release:prepare
> release:perform
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] GPDB - J2EE Multi Module Project
> [INFO] GPDB - Resources Project
> [INFO] GPDB - WAR Project
> [INFO] GPDB - EAR Project
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building GPDB - J2EE Multi Module Project
> [INFO] task-segment: [release:prepare, release:perform]
> (aggregator-style)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [release:prepare {execution: default-cli}]
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: **\pom.xml.branch, **\pom.xml.backup,
> **\pom.xml.releaseBackup, **\release.properties, **\pom.xml.next,
> **\pom.xml.tag
> [INFO] Executing: cmd.exe /X /C "scm status --username Deb --password
> *****
> --wide"
> [INFO] Working directory: C:\CALMData\Workspaces\RTC\Deb\GPDB
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Cannot prepare the release because you have local modifications :
> [/GPDB/release.properties:added]
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 24 seconds
> [INFO] Finished at: Tue May 15 20:07:09 EST 2012
> [INFO] Final Memory: 24M/81M
> [INFO]
> ------------------------------------------------------------------------
> C:\CALMData\Workspaces\RTC\Deb\GPDB>
>
> Has anything changed? This is after a release:clean.
>
> -Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org