[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] Component Reader for Locally stored Java projects
|
Hi Thomas,
how do you provide the "mc.root" property ? Can that be done by setting
up a properties file with one line like "mc.root=c:\temp\" and then
using that properties file in the cquery editor ?
Should the path for the mc.root property start with the "file:/"
protocol designator or should it just be an absolute path ?
Kind regards,
Thomas.
Thomas Hallgren wrote:
Hi Sharma,
There are two readers that you can use depending on what behavior that
you desire:
'local'
is a reader that will do no materialization at all. It will just bind
what it finds to the workspace. I.e. no copying will be performed. This
reader is ideal when Buckminster takes part as a slave in a larger
build-system and the larger system already has checked everything out to
your local system.
Here's an example of a provider set up to use a local reader set up to
use the value of the 'mc.root' property as the root.
<rm:searchPath name="default">
<rm:provider readerType="local" componentType="eclipse-project"
mutable="true" source="true">
<pv:uri format="{0}/{1}">
<bc:propertyRef key="mc.root" />
<bc:propertyRef key="buckminster.component" />
</pv:uri>
</rm:provider>
</rm:searchPath>
'url.catalog'
Assumes that your component is found using a URL root. If you use 'file'
as the protocol for this URL, you will get a reader that will
materialize from your filesystem. In contrast to the 'local' reader,
this reader will perform a true materialization, i.e. copy the material.
Example:
<rm:searchPath name="default">
<rm:provider readerType="url.catalog"
componentType="eclipse.project" mutable="true" source="true">
<pv:uri format="file:/localhome/components/{0}">
<bc:propertyRef key="buckminster.component" />
</pv:uri>
</rm:provider>
</rm:searchPath>
Kind Regards,
Thomas Hallgren
