| Re: [buckminster-dev] Plugin dependencies and cspex file |
|
You learn something new everyday. I added the following to the buckminster.cspex <alterGroups> <!-- Place your Group alterations here --> <public name="bundle.jars"> <attribute name="bundle.jars" component="OSGi_Dependency"/> <attribute name="bundle.and.fragments"/> </public> </alterGroups> And now the dependencies are built. It is a bit strange,
though, that I cannot re-order the ‘bundle.and.fragments’ attribute
(I’m assuming that a Group calls each Action in the order in which it
appears within the element), so that I actually build my dependencies first. So, to reiterate, Buckminster merely requires a dependency
to be present (as a project, or a jar, etc.), but buckminster won’t
necessarily build the dependency, unless it is explicitly told to build it. If
a project is added as a dependency in the manifest.mf file, then Buckminster assumes
that the project isn’t present, and thus builds the project into the
dependency. Thank you, Joseph Campolongo Charles River Analytics, Inc.
THIS MESSAGE IS INTENDED FOR THE USE OF THE PERSON TO WHOM IT IS ADDRESSED. IT MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If you are not the intended recipient, your use of this message for any purpose is strictly prohibited. If you have received this communication in error, please delete the message and notify the sender so that we may correct our records.
|