| Materialize appears to "remember" plugins it has installed [message #380428] |
Thu, 30 October 2008 19:33  |
 Rich Scott
Messages: 63
Registered: July 2009 |
Member |
|
|
I have been trying to track down a problem with materializing a
targetPlatform. I started with the sample that Thomas posted a year ago
http://dev.eclipse.org/newslists/news.eclipse.technology.buc kminster/msg00516.html
and have simplified it to just install 1 or 2 plugins.
The first time I run it the plugins listed in the CSPEC are materialized
exactly as I expected. If I delete the targetPlatform directory and rerun,
the feature directory is created, but no plugins. If I add an additional
plugin to the cspec and run again, that plugin is created properly. If I
then delete the platform and run the import, none of the plugins are added.
It appears that buckminster has a memory about what he has already placed
into the taretPlatform, and skips processing to restore. Is the a correct
assumption? If so, how do I get buckminster to forget or refresh its
cached state?
For reference here are my simple files
rmap:
<?xml version="1.0" encoding="UTF-8"?>
<rmap
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.eclipse.org/buckminster/RMap-1.0"
xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
xmlns:pmp="http://www.eclipse.org/buckminster/PDEMapProvider-1.0">
<searchPath name="default">
<provider readerType="eclipse.import" componentTypes="osgi.bundle"
mutable="false" source="false">
<uri
format=" http://download.eclipse.org/releases/ganymede?importType=bin ary" />
</provider>
<provider readerType="eclipse.import"
componentTypes="eclipse.feature,osgi.bundle,buckminster" source="false">
<uri
format=" http://download.eclipse.org/eclipse/updates/3.4?importType=b inary">
<bc:propertyRef key="buckminster.component" />
</uri>
</provider>
</searchPath>
<!-- Catch all others here, assuming they are in Orbit -->
<locator searchPathRef="default" pattern=".*"/>
</rmap>
mspec:
<?xml version="1.0" encoding="UTF-8"?>
<md:mspec xmlns:md="http://www.eclipse.org/buckminster/MetaData-1.0"
installLocation="c:/temp/materializer/eclipse"
materializer="targetPlatform"
name="materialize:"
url=" file:/d:/rls/eclipse/3.4/workspaces/targetPlatformTest/mater ialize/rcp.cquery "
>
</md:mspec>
cspec:
<?xml version="1.0" encoding="UTF-8"?>
<cs:cspec xmlns:cs="http://www.eclipse.org/buckminster/CSpec-1.0"
name="materialize" componentType="buckminster">
<cs:dependencies>
<cs:dependency name="org.apache.derby"
componentType="osgi.bundle"/>
<cs:dependency name="org.eclipse.draw2d"
componentType="osgi.bundle"/>
</cs:dependencies>
</cs:cspec>
cquery:
<?xml version="1.0" encoding="UTF-8"?>
<cq:componentQuery
xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
resourceMap=" file:/d:/rls/eclipse/3.4/workspaces/targetPlatformTest/mater ialize/rcp-sample.rmap ">
<cq:rootRequest name="materialize" componentType="buckminster"/>
<cq:advisorNode namePattern="materialize" useTargetPlatform="false"/>
<cq:advisorNode namePattern=".*" componentType="osgi.bundle"
useTargetPlatform="false" useWorkspace="false"/>
</cq:componentQuery>
Any insights would be appreciated.
Rich
|
|
|
| Re: Materialize appears to "remember" plugins it has installed [message #380430 is a reply to message #380428] |
Fri, 31 October 2008 07:26  |
|
Rich Scott wrote:
> I have been trying to track down a problem with materializing a
> targetPlatform. I started with the sample that Thomas posted a year ago
> http://dev.eclipse.org/newslists/news.eclipse.technology.buc kminster/msg00516.html
> and have simplified it to just install 1 or 2 plugins.
>
> The first time I run it the plugins listed in the CSPEC are materialized
> exactly as I expected. If I delete the targetPlatform directory and
> rerun, the feature directory is created, but no plugins. If I add an
> additional plugin to the cspec and run again, that plugin is created
> properly. If I then delete the platform and run the import, none of the
> plugins are added.
>
> It appears that buckminster has a memory about what he has already
> placed into the taretPlatform, and skips processing to restore. Is the a
> correct assumption? If so, how do I get buckminster to forget or refresh
> its cached state?
>
Your workspace holds meta-data in the .metadata/plugins/org.eclipse.buckminster.core
folder. Buckminster is supposed to verify that downloaded material hasn't been physically
removed. Obviously that fails and that is of course a bug.
You can manually delete the whole folder. It will rebuild itself.
Regards,
Thomas Hallgren
|
|
|
|
Powered by
FUDForum. Page generated in 0.03079 seconds
] 
Search
Help
Register
Login
Home
