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

Bug 350011

Summary:	Materializing a component from a specific subversion revision fails if the component does not exist in the HEAD revision
Product:	z_Archived	Reporter:	Matthew Webber <matthew>
Component:	Buckminster	Assignee:	buckminster.core-inbox <buckminster.core-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	dh_tue, matthew, thomas
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Matthew Webber

2011-06-22 03:56:07 EDT

Build Identifier: Version: Helios Service Release 2, Build id: 20110301-1815

In my CQuery, I have an advisor node specifying that components should be resolved from a specific subversion revision. This fails when resolution attempts to locate a component which does exist in the requested revision, but does not exist in HEAD (in my case, the component was renamed).

The problem (and solution) can be illustrated fairly simply from the subversion command line. Imagine I want to check out old.plugin.name, which exists in revision 12345, but not in the HEAD revision.

This command will fail:
svn checkout -r12345 https://server/project/trunk/plugins/old.plugin.name

The command you actually want is:
svn checkout -r12345 https://server/project/trunk/plugins/old.plugin.name@12345
Subversion calls the "@12345" a "peg revision".

It looks to me like buckminster uses the first form rather than the second.




Reproducible: Always

Comment 1 Thomas Hallgren

2011-06-30 07:16:46 EDT

Are you using Subclipse or Subversive ?

Comment 2 Matthew Webber

2011-06-30 08:04:10 EDT

(In reply to comment #1)
> Are you using Subclipse or Subversive ?
I am using Subclipse.

Comment 3 Thomas Hallgren

2011-07-03 09:11:24 EDT

Buckminster is now using PEG revisions during resolve.

http://git.eclipse.org/c/buckminster/buckminster.git/commit/?id=80bc1159ef38de310abdd20a2abad63dd95afd34