Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 177078

Summary: [relengtool] Releng release tool doesn't handle out-of-sync map file well
Product: [Eclipse Project] Platform Reporter: Walter Harley <eclipse>
Component: RelengAssignee: Platform-Releng-Inbox <platform-releng-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P5 CC: kim.moir, Michael.Valenta
Version: 3.3Keywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Walter Harley CLA 2007-03-12 19:09:05 EDT
Reporting against the N20070310-0010 build of the releng tools.

I tried using the releng release tool to release my plugins.  However, my map file was not up to date.  What happened was that the release wizard made it all the way to the final pane and then reported an error from CVS saying the map file was out of sync.  At that point I still had the release tool wizard up on the screen, giving me the option to either go back or finish, but neither of those options would allow me to fix the problem; I assume that hitting finish would have just given me another CVS error, though I didn't try.  

To fix the problem I had to cancel out of the release wizard (leaving me in an unclear state - were my projects tagged or not?), and manually update the map file and deal with merge conflicts.  Trying to release the projects again with the tool failed, because it complained that the build-notes.html file contained uncommitted changes.  So I ended up manually committing the build-notes.html and the map file, and manually retagging the affected project (so that build-notes.html would be included in the release).

Expected: the wizard should start out by checking whether the map files are up to date, and if not, should either abort at that point or permit the user to handle the conflict.
Comment 1 Kim Moir CLA 2012-03-01 11:06:10 EST
With the move to Git, this tool isn't in active use anymore for anything other than copyright updates.  I'm going to close this bug as we have no plans to address it.