[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] component binding
|
One thing is important to remeber. Buckminster does not stipulate that a
component needs to be a project, nor that it must become one when it is
materialized. Some artifacts are never bound at all. All artifacts are
however known to Buckminster (i.e. stored in meta-data) once they are
successfully materialized. The methods that you mention does not only
apply to projects. They can also be used on artifacts that are
materialized but not projects as such. Buckminster will normally put
such artifacts under the umbrella project ".buckminster" so that they
can be accessed using the Eclipse navigator. Perhaps what you are trying
to achieve here is simply a non-project construction?
Buckminster will only use the natures to determine the CSpecPacking
builder when the component in question indeed is an eclipse project
component.
- thomas
Knut Wannheden wrote:
Ken,
On 1/18/06, Kenneth Ölwing <kenneth@xxxxxxxxx> wrote:
Now this starts to sound a lot like the discussion we had in december.
Already then you suggested adding a "binders" extension point. I
didn't remember that until just now. Sorry about that. My problem now
seems to be yet another, slightly different, usecase for this
"binders" extension point.
Is the sole reason for attaching a nature to the project so that you
possibly can recognize it later? If so, perhaps you somehow could instead
make use of the metadata instead (through IWorkspaceInfo in core)?
The reason is that I'd like Buckminster to recognize the components
later. When I run a component query Buckminster seems to check whether
any of the required components already exist in the workspace
(ResourceMap#getCSpecPacking(NodeQuery)). If they do it will look up
the cspec builder using the project's list of natures
(CorePlugin#getCSpecPackingBuilder(String[])). So I don't see how I
could use metadata instead.
--knut
_______________________________________________
buckminster-dev mailing list
buckminster-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/buckminster-dev
