| Materialize from SVN branch [message #836261] |
Wed, 04 April 2012 05:37  |
Eclipse User |
|
|
|
Hi,
I want to materialize a project from a svn branch but the svn structure looks a bit complicated: /trunk/long/path/to/<module> and /branches/long/path/to/<branch>/<module>.
First, I tried to put the branch path into my rmap search path (leading h ttps: // removed):
<rm:searchPath name="">
<rm:provider componentTypes="osgi.bundle,eclipse.feature,buckminster" readerType="svn">
<rm:uri format="svn.nowhere.com/branches/long/path/to/branch_name/{0}">
<bc:propertyRef key="buckminster.component"/>
</rm:uri>
</rm:provider>
</rm:searchPath>
which gives me a URL_NON_EXISTENT exception because buckminster modified the url and searches for the module in /trunk/long/path/to/branch_name/<module>. (Why?, I would expect it should use exact the path given because no 'trunk' is included.)
Next I tried to put the correct path to trunk in the rmap search path and use an advisor node with an selection criteria/branch name but failed because buckminster than searches the branch name in /branches/<branch> and it is impossible to use a branch path for the selection criteria; slashes are forebidden.
So, how is it possible to use the svn reader type for these svn structure?
Thanks.
Edit: s#/branch/#/branches/#g
[Updated on: Wed, 04 April 2012 06:20] by Moderator |
|
|
| Re: Materialize from SVN branch [message #836443 is a reply to message #836261] |
Wed, 04 April 2012 09:45  |
| Eclipse User |
|
|
|
HI Aleksandr,
You must use the word 'trunk' in the uri. Buckminster uses that works as a hint of where to find 'branches' and 'tags'.
Also, be careful to use the URI fragment for the actual project. Example:
<rm:uri format="svn.nowhere.com/trunk/long/path/to?moduleBeforeBranch#{0}">
Then use a branch selector in your cquery to tell Buckminster to search for a specific branch. Buckminster will divide
this URL into three parts.
1. "svn.nowhere.com/"
This is the path to where Buckminster expects to find 'trunk', 'branches' or 'tags'.
2. '/long/path/to'
This is the 'module path'. It will either added before or after the branch name depending on the flag moduleBeforeBranch
or moduleAfterBranch. You seem to need the former.
3. The component name (i.e the {0})
The full URI is then re-assembled by Buckminster as:
1/2/<branch from cquery>/3
which in your case would resolve to:
svn.nowhere.com/branches/long/path/to/<branch>/{0}
HTH,
- thomas
On 04/04/2012 11:37 AM, aleksandr skeuse wrote:
> Hi,
>
> I want to materialize a project from a svn branch but the svn structure looks a bit complicated:
> /trunk/long/path/to/<module> and /branch/long/path/to/<branch>/<module>.
>
> First, I tried to put the branch path into my rmap search path (leading h ttps: // removed):
>
> <rm:searchPath name="">
> <rm:provider componentTypes="osgi.bundle,eclipse.feature,buckminster" readerType="svn">
> <rm:uri format="svn.nowhere.com/branch/long/path/to/branch_name/{0}">
> <bc:propertyRef key="buckminster.component"/>
> </rm:uri>
> </rm:provider>
> </rm:searchPath>
>
> which gives me a URL_NON_EXISTENT exception because buckminster modified the url and searches for the module in
> /trunk/long/path/to/branch_name/<module>. (Why?, I would expect it should use exact the path given because no 'trunk' is
> included.)
>
> Next I tried to put the correct path to trunk in the rmap search path and use an advisor node with an selection
> criteria/branch name but failed because buckminster than searches the branch name in /branch/<branch> and it is
> impossible to use a branch path for the selection criteria; slashes are forebidden.
>
> So, how is it possible to use the svn reader type for these svn structure?
>
> Thanks.
|
|
|
|
|
|
|
| Re: Materialize from SVN branch [message #848674 is a reply to message #847401] |
Wed, 18 April 2012 09:24 |
| Eclipse User |
|
|
|
Hi Thomas,
again, thank you for your help.
But how would this explain why it is running with bm 3.6 + subversive svn client? The bug report is bm 3.7 related so after reading it I would expect both, bm 3.6 subversive and subclipse client versions to work.
Do you have a fix for 372822 and if so, in which version of buckminster it will be included?
|
|
|
Powered by
FUDForum. Page generated in 0.20132 seconds
Home