[buckminster-dev] Materializing workspace using PDEMapProvider

[Todd_Lee@xxxxxxxx]

Hi there,

As an initial task, I'd like to try using Buckminster to materialize a new
developer workspace (just like the Harry/Tom usage case on the wiki).
Currently we use team project sets/PDE maps in our own 'org.eclipse.releng'
bundle. The documentation is not completely clear as to how one might
leverage the maps when resolving dependencies and materializing a
workspace.

To an example:

we've got /folder/path/in/cvs/org.eclipse.releng

which, when checked out has a number of sub directories including a map
directory ie -

org.eclipse.releng/
      |-maps/
           |- platform.map  (declares feature: 'my.com.platform-feature'
and plugin 'my.com.platform'
           .... more .map files

Of course, the workspace includes source for many features/plugins etc,
spread across a number of the .map files (essentially grouped by
feature...)

Looking at the documentation, I'm not entirely certain as to the best way
to materialize all of these components using the map files. Do I need a
single cspec that declares all of the features as dependencies and then use
the PDEMapProvider to resolve the actual components? Kind of in the dark
here...

If you can point me in the direction of some more in depth documentation
regarding the use of the PDEMapProvider, or even better yet, some examples,
I'd be very grateful!

Thanks
Todd


AMI Semiconductor - "Silicon Solutions for the Real World"
NOTICE: 
This electronic message contains information that may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you received this electronic message in error, please notify the sender and delete the copy you received.