[news.eclipse.technology.buckminster] Re: CSpec Editor read-only

[Thomas Hallgren <thomas@xxxxxxx>]

I right-click on a component and choose "Buckminster" -> "View CSpec", you will see Buckminsters 
notion of the meta-data for that component in the form of a cspec. Normally that notion doesn't map 
to a file. Instead Buckminster shows you meta-data that it extracts from other files like the 
manifest, a plugin.xml etc. In order to change that particular meta-data, you need to change the 
file original files, not the cspec view. Hence the read-only status.

For some projects (i.e. non plug-in or feature projects), Buckminster doesn't see any meta-data. In 
that case, you need to provide this meta-data manually. This is done by providing a file that is 
named "buckminster.cspec". It must have that exact name, or Buckminster will not find it (this 
behavior is similar to what the Eclipse IDE does with plugin.xml, feature.xml, .project, .classpath, 
or what Maven does with pom.xml. You can't rename them either).

If you have some other name like SubversionTools.cspec, Buckminster will not be able to see the file 
at all. You will still be able to obtain a read-only view of a cspec but it has no correlation with 
the file.

What behavior would you like to see in Buckminster?

Regards,
Thomas Hallgren


Jonathan Gossage wrote:
> I am new to Buckminster and I am trying to publish a very simple 
> component which is housed in a generic Eclipse project. Initially, when 
> I reied to create the .cspec file I gave the .cspec file the same name 
> as the Eclipse project, namely 'SubversionTools'. When I did this I 
> found that the .cspec file was always loaded into the Cspec editor as 
> read-only so no changes could be saved.
>
> If, instead, I accepted the default name for the .cspec file, namely 
> buckminster.cspec I was able to edit te file in the Cspec editor. Is 
> this expected behaviour as it seems to be quite brittle to me?
>
> Regards
>
> Jonathan Gossage