Community
Participate
Working Groups
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
Are you using Subclipse or Subversive ?
(In reply to comment #1) > Are you using Subclipse or Subversive ? I am using Subclipse.
Buckminster is now using PEG revisions during resolve. http://git.eclipse.org/c/buckminster/buckminster.git/commit/?id=80bc1159ef38de310abdd20a2abad63dd95afd34