[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[buckminster-dev] Re: Bucminster nature - what does it really do?
|
ok - issue #166078 created.
- henrik
"Thomas Hallgren" <thomas@xxxxxxx> skrev i meddelandet
news:ekhm1p$hfg$1@xxxxxxxxxxxxxxxxx...
> There was a time when we thought that given an Eclipse project (a project
> that has a ProjectDescriptor, i.e. the .project file), we could actually
> determine the type of that project just by looking at the natures. Little
> did we know about the Eclipse platform projects :-) Their project
> descriptors are empty... As it turns out, the only way to determine the
> type of project is to look for the contents of specific files such as
> feature.xml, META-INF/MANIFEST.MF etc. Albeit a bit slower, it is also
> more secure.
>
> So to answer your question, we currently don't use the Buckminster nature
> for anything and it should be removed altogether. Can you please enter a
> bugzilla on this?
>
> - thomas
>
>
> Henrik Lindberg wrote:
>> Remind me again, why do we have a Buckmisnter Nature? Does it do anything
>> except create a .cspec if there is none already?
>> Removing the Buckminster nature does not seem to have any effect for
>> instance.
>>
>> Why not simply remove it?
>>
>> I am working on a proposal (that I will post on the wiki with a link
>> here) to have a Buckminster "Buckminster Project Manager" (or somesuch
>> name) that helps you check what Buckmisnter can do with a project, and
>> aid if there are things like a .cspec needed to be able to manage the
>> project.
>>
>> I think it would be easier to explain (and to understand) how things work
>> without the Buckminster Nature thing (esp. if it does not do anything,
>> and if it does, that needs to be exapplained).
>>
>> - henrik
>>
>> _______________________________________________
>> buckminster-dev mailing list
>> buckminster-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>>