|Re: Materializing non-Java and non-plugin projects [message #630120 is a reply to message #630046]
||Thu, 30 September 2010 16:16
| Henrik Lindberg
Registered: July 2009
For component types that are not already supported (i.e. features, |
plugins, maven components etc.) you can use the buckminster component
type. Simply create a project (a general purpose project will do just
fine), and create a buckminster .cspec file in this project's root.
In this cspec you declare all of your dependencies and the actions you
want to be able to execute on this component.
In your rmap you use buckminster as component type for such components.
I hope this helps as a starting point.
On 9/30/10 3:51 PM, Vlad Dumitrescu wrote:
> The Buckminster docs say that a component can be anything, but I
> couldn't find any example of a component being something else than a
> plugin or feature... The chapter for "Non Java Projects" in the book is
> Is there some information somewhere that I didn't find, or am I on my own?
> I am trying to use Buckminster as a build tool, to import my projects in
> a workspace and build them there, because some of the builders are not
> available as ant tasks or similar and I need to build everything headless.
> best regards,
Powered by FUDForum
. Page generated in 0.10099 seconds