Editing an rmap containing a git provider corrupts the rmap XML [message #645530] |
Fri, 17 December 2010 16:55  |
Eclipse User |
|
|
|
I have an rmap that contains the following git provider:
<rm:provider componentTypes="unknown" readerType="git" resolutionFilter="(use_git_for_GDALargeTestFiles=yes)">
<rm:uri format="{0}/GDALargeTestFiles">
<bc:propertyRef key="workspace.root"/>
</rm:uri>
<rm:property key="git.remote.uri" value="git://hudson:9418/GDALargeTestFiles"/>
<rm:property key="git.auto.fetch" value="true"/>
</rm:provider>
Note that, within the provider, the uri element comes first, followed by the two property elements. This is correct according to the schema.
If I then edit the rmap using the Buckminster editor, and change anything in the rmap, then when the rmap is saved it reverses the order, and puts the property keys before the uri key. Any subsequent attempt to use the rmap gives errors as the rmap is invalid according to the schema.
This is with the Eclipse Buckminster feature 1.3.1.r11621, in Helios SR1, on Linux.
Has anyone else encountered this? I'm fairly new to Buckminster (and loving it), but this looks like a straight bug.
Thanks
Matthew
|
|
|
Re: Editing an rmap containing a git provider corrupts the rmap XML [message #645568 is a reply to message #645530] |
Sat, 18 December 2010 01:59   |
Eclipse User |
|
|
|
Sure sounds like a bug. Please file a bugzilla.
- henrik
On 12/17/10 5:56 PM, Matthew Webber wrote:
> I have an rmap that contains the following git provider:
>
> <rm:provider componentTypes="unknown" readerType="git"
> resolutionFilter="(use_git_for_GDALargeTestFiles=yes)">
> <rm:uri format="{0}/GDALargeTestFiles">
> <bc:propertyRef key="workspace.root"/>
> </rm:uri>
> <rm:property key="git.remote.uri"
> value="git://hudson:9418/GDALargeTestFiles"/>
> <rm:property key="git.auto.fetch" value="true"/>
> </rm:provider>
>
> Note that, within the provider, the uri element comes first, followed by
> the two property elements. This is correct according to the schema.
>
> If I then edit the rmap using the Buckminster editor, and change
> anything in the rmap, then when the rmap is saved it reverses the order,
> and puts the property keys before the uri key. Any subsequent attempt to
> use the rmap gives errors as the rmap is invalid according to the schema.
>
> This is with the Eclipse Buckminster feature 1.3.1.r11621, in Helios
> SR1, on Linux.
>
> Has anyone else encountered this? I'm fairly new to Buckminster (and
> loving it), but this looks like a straight bug.
>
> Thanks
> Matthew
>
>
>
|
|
|
Re: Editing an rmap containing a git provider corrupts the rmap XML [message #645602 is a reply to message #645568] |
Sat, 18 December 2010 15:20   |
Eclipse User |
|
|
|
There are some other rmap editor/XSD inconsistencies already reported in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=330498 so please add a
comment to that bugzilla.
Regards,
Thomas Hallgren
On 2010-12-18 02:59, Henrik Lindberg wrote:
> Sure sounds like a bug. Please file a bugzilla.
> - henrik
>
> On 12/17/10 5:56 PM, Matthew Webber wrote:
>> I have an rmap that contains the following git provider:
>>
>> <rm:provider componentTypes="unknown" readerType="git"
>> resolutionFilter="(use_git_for_GDALargeTestFiles=yes)">
>> <rm:uri format="{0}/GDALargeTestFiles">
>> <bc:propertyRef key="workspace.root"/>
>> </rm:uri>
>> <rm:property key="git.remote.uri"
>> value="git://hudson:9418/GDALargeTestFiles"/>
>> <rm:property key="git.auto.fetch" value="true"/>
>> </rm:provider>
>>
>> Note that, within the provider, the uri element comes first, followed by
>> the two property elements. This is correct according to the schema.
>>
>> If I then edit the rmap using the Buckminster editor, and change
>> anything in the rmap, then when the rmap is saved it reverses the order,
>> and puts the property keys before the uri key. Any subsequent attempt to
>> use the rmap gives errors as the rmap is invalid according to the schema.
>>
>> This is with the Eclipse Buckminster feature 1.3.1.r11621, in Helios
>> SR1, on Linux.
>>
>> Has anyone else encountered this? I'm fairly new to Buckminster (and
>> loving it), but this looks like a straight bug.
>>
>> Thanks
>> Matthew
>>
>>
>>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.06379 seconds