maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte" <apa...@sourcegrounds.com>
Subject Re: Jazz SCM issues with the MRP 2.3.1
Date Fri, 08 Jun 2012 20:21:57 GMT
Hi Chris,

I'd like to do a 2.3.2 release somewhere next week.
Could you investigate this issue?

-Robert

Op Sat, 02 Jun 2012 12:24:01 +0200 schreef Chris Graham  
<chrisgwarp@gmail.com>:

> Now that I have my VM (where I've done all of my jazz development) back  
> able to talk to the Internet, I'll give it a go.
>
> -Chris
>
> Sent from my iPhone
>
> On 02/06/2012, at 6:17 PM, "Robert Scholte" <apache@sourcegrounds.com>  
> wrote:
>
>> Hi Chris,
>>
>> can you confirm that the  
>> org.apache.maven.shared.release.scm.JazzScmTranslator.toRelativePath(String)  
>> is executed?
>> I've written unittests for this method, which reflect your usecase.  
>> Have a look at them too.
>>
>> -Robert
>>
>> Op Sat, 02 Jun 2012 05:46:14 +0200 schreef Chris Graham  
>> <chrisgwarp@gmail.com>:
>>
>>> Hi All.
>>>
>>> Sorry for that the fact that it's taken me so long to get around to  
>>> testing
>>> the 2.3.1 release plugin, but my laptop had some 'firewall issues' that
>>> needed to be resolved by IBM.
>>>
>>> So, I checked out a new jazz workspace, and attempted my first release  
>>> in
>>> it, and this is what I got:
>>>
>>> C:\tmp\release-workspace\GPDB>mvn -B -Dresume=false
>>> -DworkingDirectory=C:\tmp\maven release:prepare release:perform
>>> [INFO] Scanning for projects...
>>> [INFO] snapshot au.com.warpspeed:warpspeed-dynamic-parent:1-SNAPSHOT:
>>> checking for updates from warpspeed.repos
>>> [WARNING] repository metadata for: 'snapshot
>>> au.com.warpspeed:warpspeed-dynamic-parent:1-SNAPSHOT' could not be
>>> retrieved from repository: warpspeed.repos due to an
>>> error: Authorization failed: Access denied to:
>>> http://archiva.warpspeed.com.au/archiva/repository/warpspeed.repos/au/com/warpspeed/warpspeed-dynamic-parent/1-SNAPSHO
>>> T/maven-metadata.xml
>>> [INFO] Repository 'warpspeed.repos' will be blacklisted
>>> [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:\tmp\release-workspace\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: 1 minute 11 seconds
>>> [INFO] Finished at: Sat Jun 02 13:24:59 EST 2012
>>> [INFO] Final Memory: 24M/71M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> C:\tmp\release-workspace\GPDB>
>>>
>>>
>>> So, it appears that it is still not ignoring some of the temporary  
>>> files in
>>> the release process. What that what some of the new methods were meant  
>>> to
>>> address? Or have I missed something?
>>>
>>> Here is the output of the "scm status" command that is used to  
>>> determine
>>> the status of files.
>>>
>>> C:\tmp\release-workspace\GPDB>scm status
>>> Workspace: (1156) "GPDBWorkspace" <-> (1157) "GPDBStream"
>>>  Component: (1158) "GPDB" <-> (1157) "GPDBStream"
>>>    Baseline: (2222) 36 "GPDB-1.0.36"
>>>    Unresolved:
>>>      a-- /GPDB/release.properties
>>>
>>> C:\tmp\release-workspace\GPDB>
>>>
>>> This is what is being processed, and you can see the output of the mvn
>>> scm:status command:
>>>
>>> C:\tmp\release-workspace\GPDB>mvn scm:status
>>> [INFO] Scanning for projects...
>>> [INFO] snapshot au.com.warpspeed:warpspeed-dynamic-parent:1-SNAPSHOT:
>>> checking for updates from warpspeed.repos
>>> [WARNING] repository metadata for: 'snapshot
>>> au.com.warpspeed:warpspeed-dynamic-parent:1-SNAPSHOT' could not be
>>> retrieved from repository: warpspeed.repos due to an
>>> error: Authorization failed: Access denied to:
>>> http://archiva.warpspeed.com.au/archiva/repository/warpspeed.repos/au/com/warpspeed/warpspeed-dynamic-parent/1-SNAPSHO
>>> T/maven-metadata.xml
>>> [INFO] Repository 'warpspeed.repos' will be blacklisted
>>> [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: [scm:status] (aggregator-style)
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [scm:status {execution: default-cli}]
>>> [INFO] Executing: cmd.exe /X /C "scm status --username Deb --password  
>>> *****
>>> --wide"
>>> [INFO] Working directory: C:\tmp\release-workspace\GPDB
>>> [INFO] added status for /GPDB/release.properties
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD SUCCESSFUL
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 28 seconds
>>> [INFO] Finished at: Sat Jun 02 13:34:00 EST 2012
>>> [INFO] Final Memory: 17M/48M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> C:\tmp\release-workspace\GPDB>
>>>
>>> The only workaround so far that I've been able to do is to add
>>> 'release.properties' to the .jazzignore file, so that jazz itself  
>>> ignores
>>> the file (much like the svn.ignore property). The file '.jazzignore'  
>>> now
>>> looks something like this:
>>>
>>> ### Jazz Ignore 0
>>> # Default value for core.ignore.recursive is *.class
>>> #  Changing this value changes check-in behaviour for the entire  
>>> project.
>>> #
>>> # Default value for core.ignore is bin
>>> #  Changing this value changes check-in behaviour for the local  
>>> directory.
>>> #
>>> # Ignore properties should contain a space separated list of filename
>>> patterns.
>>> # Each pattern is case sensitive and surrounded by braces ('{' and  
>>> '}').
>>> # "*" matches zero or more characters, and "?" matches single  
>>> characters.
>>> #
>>> #   e.g: {*.sh} {\.*}    ignores shell scripts and hidden files
>>>
>>> # NOTE: modifying ignore files will not change the ignore status of  
>>> derived
>>> # resources.
>>>
>>> core.ignore.recursive= \
>>>    {*.class} \
>>>    {*.log}
>>>
>>> core.ignore= \
>>>    {release.properties} \
>>>    {target}
>>>
>>> -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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message