| Re: [buckminster-dev] Materializing workspace using PDEMapProvider [message #3401] |
Wed, 13 February 2008 14:15 |
Eclipse User |
|
|
|
Thanks for the reply Thomas,
I did see your dogfood2 rmap, and I'm using that as a template. I'm trying
to understand the nature of the matching though.
We have only one map directory, with many .map files. So if I create a top
level buckminster.cspec that declares dependencies on my top level features
(and as you said, lower level features/plugins will be handled
transitively) does buckminster check all of the .map files in the map
folder as specified in the provider uri?
eg
- my cspec declares a dependency on 'my.com.platform-feature'
(componentType eclipse.feature)
- I have the following map files: platform.map (which actually includes the
above feature and it's required plugins etc) along with feature2.map and
feature3.map.
Is there any regex matching to find a particular map file for my declared
dependency on my.com.platform-feature (ie - do I have to somehow 'map' the
component name to the correct map file?) or does buckminster just check
*.map in the maps directory to find an appropriate match?
Thanks
Todd
Todd Lee
Software Tools
AMI Semiconductor
Tel: +1.519.884.9696 ext 2242
Fax: +1.519.884.0228
E-mail: todd_lee@amis.com
Thomas Hallgren
<thomas@tada.se>
Sent by: To
buckminster-dev-b Buckminster developer discussions
ounces@eclipse.or <buckminster-dev@eclipse.org>
g cc
Subject
02/13/2008 01:59 Re: [buckminster-dev] Materializing
PM workspace using PDEMapProvider
Please respond to
Buckminster
developer
discussions
<buckminster-dev@
eclipse.org>
Hi Todd,
Our own RMAP, the
http://www.eclipse.org/buckminster/samples/rmaps/dogfood2.rm ap can be a
good
source of information. Look at the provider for org.eclipse.ecf. That
single provider will be able
to find all sources that ECF maps using their PDE maps.
In a PDEMapProvider, the <uri format="..."> must point to the folder
containing the maps. If you
have several such folders, you need several providers. It's up to you if
you want to use one single
searchPath that includes many providers or if you want to have a more
fine-grained resolution that
uses several searchPaths with one provider in each. The latter is likely to
resolve quicker but it
requires some natural way of defining locator patterns based on component
names.
Buckminster is capable of resolving things transitively. So if you have a
component A with
dependenceis to B and C, you only need to query for A for all three to be
materialized. A in this
case may for instance be an Eclipse feature listing other features or
plug-ins or an eclipse plug-in
with "Require-Bundle" clause in its manifest.
If you don't have a natural top-level feature, you can create a
buckminster.cspec that has
dependencies to your top-level components. I don't know how your component
hierarchy is constituted
but in most cases you don't have to list more then a few top-level
components. The rest will be
brought in transitively.
Regards,
Thomas Hallgren
Todd_Lee@amis.com wrote:
> 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.
>
_______________________________________________
buckminster-dev mailing list
buckminster-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/buckminster-dev
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.
|
|
|
Powered by
FUDForum. Page generated in 0.03065 seconds
Home