|Re: Having cspec and cspex in one feature [message #554277 is a reply to message #554268]
||Fri, 20 August 2010 21:17
| Henrik Lindberg
Registered: July 2009
Buckminster generates actions based on the component type and the meta |
data it discovers. You can see what is generated per component type in
the reference section of the Bucky Book (or just view the cspec for a
Any component with a generated cspec can have a cspex that "decorates"
the generated specification. In a component of type "buckminster"
everything is placed in the cspec manually (and a cspex is superfluous
in this case).
The rmap is the starting point - it is here buckminster is told how it
should find, discover and generate a cspec given a name, type, and
version of a component.
On 8/20/10 10:41 PM, Alex wrote:
> I followed bucky book to create legacy update site project - everything
> works. My question is, is it possible to incorporate cspec from update
> site project to another project that includes cspex? I tried copying
> cspec, index.html and site.xml to my other project but get error that
> site.p2 could not be found, renaming from buckminster.cspec to another
> name stopped the error, but when I bring up actions in the project I
> don't site build.site action. How does buckminster know for example to
> make build.site available in the update site project and not in another
> that contains cspec and updated .project properties that includes update
> site nature (not sure if .project is important here though)?
> I am not sure what I did is correct or allowed, was just trying
> different things to make this work.
Powered by FUDForum
. Page generated in 0.03484 seconds