[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[buckminster-dev] Relative URI for local readerType in provider search path
|
Hi All,
I'm a new user to buckminster and I've been banging my head around coming up with a clean solution to importing local set of projects checked out in local directory via a perforce provider. Since the buckminster p4 provider is no longer available, I am trying to use the local reader to materialize a set of plugin projects.
My rmap and cquery files are already relative to where the projects are checked out, and I was hoping there is a buckminster equivalent to ANT's ${basedir} property. I can't use workspace.root, since the projects haven't been materialized into the eclipse workspace yet. I don't want to hard-code the absolute URI since developers checkout the sources to different locations on their workstations.
I was hoping I could write something similar to the following, but it doesn't seem possible:
<searchPath name="localbundles">
<provider componentTypes="osgi.bundle" readerType="local" source="true" mutable="true">
<uri format="{0}/../bundles/{1}">
<bc:propertyRef key="basedir"/> <!-- what do I use here??? -->
<bc:propertyRef key="buckminster.component"/>
<uri>
<!-- using a path relative to the rmap location doesn't work either -->
<uri format="../bundles/{0}">
<bc:propertyRef key="buckminster.component"/>
<uri>
</provider>
</searchPath>
Thanks in advance for any feedback
--Mike
This E-mail and any of its attachments may contain Time Warner
Cable proprietary information, which is privileged, confidential,
or subject to copyright belonging to Time Warner Cable. This E-mail
is intended solely for the use of the individual or entity to which
it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination,
distribution, copying, or action taken in relation to the contents
of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any
copy of this E-mail and any printout.