A component defines a set of named attributes. Each attribute is either an _artifact_ that appoints pre-existing files and directories, an _action_ that describes something that can be done in order to produce new artifacts, or a _group_ which is an arbitrary grouping of _artifact_, _action_, and _group_ instances. A component also defines a list of _dependencies_ to other components. Such dependencies are referred from _action_ prerequisites and _groups_ The key of the dependencies The foreign key between an external action or group prerequisite and a dependency. The foreign key between the dependency obtainedFrom and another dependency. A resolution request for another component The name of the component. This name is required if the request has no import elements The component type, if any, of the required component. The version designator, if any, of the required component The type of versions used in the version designator The name of the required attribute The version designator, if any, of the required attribute The name to use for properties and filesets that reflect the product Base of all paths, relative to component root The id of the actor. Lack of this attribute indicates a predefine internal action Used to turn on/off the timestamp dependent execution Used to tell the framework if it should assign the actor a stream it can print to LDAP filter controlling if this action is enabled or disabled Deprecated and ignored A definition defines an attribute as something that is part of another attribute. A good example is a Java package that is part of a jar file.
The Define is very similar to an OSGi manifest Export-Package Base of all paths, relative to component root LDAP filter controlling if this artifact is enabled or disabled Defines the type for this artifact LDAP filter controlling if this group is enabled or disabled New base to use on all local paths where possible. Paths not parented by this base are left "as is", i.e. the path group they belong to will not change. New base to use on all local paths where possible. Paths not parented by this base are left "as is", i.e. the path group they belong to will not change. The alias to pass along to the actor The attribute name in the appointed component The name of a dependency when this prerequisite extends beyond the cspec where it is declared. The type of a dependency when this prerequisite extends beyond the cspec where it is declared. The name to use for properties and filesets that reflect this requirement Set to true if the artifact is optional. A regular expression controlling exclusion of component attributes A regular expression controlling inclusion of component attributes An OSGi filter controlling inclusion of the prerequisite Set to false if we only want to trigger the referenced attribute but have no interest in what it produces. The up to date policy tells Buckminster how to go about determining the timestamp of a product when deciding if it is up to date in respect to its prerequisites. Never trust a product defined as a folder since the expected number of files is unknown Let the actor decide. Some system internal actors like the FragmentsActor uses this. Trust timestamp only when the product contains the number of files denoted in attribute 'count' Trust timestamp of a product that matches the action prerequisites in number and optional pattern. The 'count' attribute may be used to denote file additions Trust timestamp of any product that contains at least one file