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

Bug 178720

Summary:	[relengtool] release tool's "load map projects" doesn't work quite right if more than one version in map file
Product:	[Eclipse Project] Platform	Reporter:	David Williams <david_williams>
Component:	Releng	Assignee:	Platform-Releng-Inbox <platform-releng-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	dj.houghton, kim.moir, Michael.Valenta
Version:	3.3	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description David Williams

2007-03-22 00:14:42 EDT

The use case I'd like to see supported is that the "load map projects" honor the preference that says "use .project project name instead of module name". 

I'm not sure if this _ever_ worked, (I thought it used to, but I'm using version I20070321-1300 and doesn't seem to work for any project). 

But ... the case I happened to be checking was when there was multiple versions per map file, and each version had the package version in it's name element, in the .project file. For example, 

plugin@javax.servlet,2.3.0=v200703220341,:pserver:anonymous@dev.eclipse.org:/cvsroot/tools,,org.eclipse.orbit/javax.servlet
plugin@javax.servlet,2.4.0=v200703220344,:pserver:anonymous@dev.eclipse.org:/cvsroot/tools,,org.eclipse.orbit/javax.servlet


It worked correctly if I directly checked out those versions from CVS (loading both in workspace, each with slightly different project name, as per their .project files). But, if I used "load map project", it just loaded one ... well, it probably loaded both but just overwrote first one with second one.

Comment 1 DJ Houghton

2007-03-22 09:28:15 EDT

See also bug 173314.

I haven't tested the "Load Map Projects" feature yet. (didn't know it existed until yesterday :-)

Comment 2 Kim Moir

2012-03-01 11:06:38 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.