Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster dev » [buckminster-dev] Strange resolver behaviour when resolving PDE plugins - using "native" t
[buckminster-dev] Strange resolver behaviour when resolving PDE plugins - using "native" t [message #18771] Mon, 26 May 2008 14:48
Mikhail Kadan is currently offline Mikhail Kadan
Messages: 61
Registered: July 2009
Member
------=_Part_4204_11413542.1211813309325
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi.

I have found strange resolver behaviour when resolving standard PDE plugins.

1) Created empty target platform with minimal set of plugins
("org.eclipse.osgi", etc.)
2) Switched workspace to this new target platform
3) Created plugin named "org.apache.log4j" (version "1.0.0") and put it to
SVN
4) Created RMAP and CQUERY to this materialize this plugin
5) Executed CQUERY and got strange "org.apache.log4j" with version "1.2.13"
!!!

According to Buckminster log, there was no query to my SVN at all:

registered serializer org.jabsorb.serializer.impl.RawJSONArraySerializer
registered serializer org.jabsorb.serializer.impl.RawJSONObjectSerializer
registered serializer org.jabsorb.serializer.impl.BeanSerializer
registered serializer org.jabsorb.serializer.impl.ArraySerializer
registered serializer org.jabsorb.serializer.impl.DictionarySerializer
registered serializer org.jabsorb.serializer.impl.MapSerializer
registered serializer org.jabsorb.serializer.impl.SetSerializer
registered serializer org.jabsorb.serializer.impl.ListSerializer
registered serializer org.jabsorb.serializer.impl.DateSerializer
registered serializer org.jabsorb.serializer.impl.StringSerializer
registered serializer org.jabsorb.serializer.impl.NumberSerializer
registered serializer org.jabsorb.serializer.impl.BooleanSerializer
registered serializer org.jabsorb.serializer.impl.PrimitiveSerializer
org.apache.log4j:osgi.bundle: Using resolver rmap
Found two entries for component org.eclipse.equinox.registry:osgi.bundle.
Version 3.3.0.v20070522 located at
C:/Work/go-product/GO/platform/plugins/org.eclipse.equinox.r egistry_3.3.0.v20070522.jar
and version 3.3.1.R33x_v20070802 at
C:/Work/go-product/GO/platform/plugins/org.eclipse.equinox.r egistry_3.3.1.R33x_v20070802.jar
Found two entries for component org.eclipse.core.expressions:osgi.bundle.
Version 3.2.2.r322_v20070109a located at
C:/Work/go-product/GO/platform/plugins/org.eclipse.core.expr essions_3.2.2.r322_v20070109a.jar
and version 3.3.0.v20070606-0010 at
C:/Work/go-product/GO/platform/plugins/org.eclipse.core.expr essions_3.3.0.v20070606-0010.jar

6) Found "org.apache.log4j" with version "1.2.13" in my Eclipse installation
target platform.
7) Changed "org.apache.log4j" version to "2.0.0" in SVN
8) Executed CQUERY and got my plugin from SVN


So I can made a conclusion, that Buckminster also searches his "native"
target platform (target platform which was used to start Eclipse), and if it
finds a match here, which has bigger version than others, it will try to
materialize this plugin from "native" platform. As such plugin has no source
code (most of the times), there will be nothing materialized to workspace
and the whole project will fail to launch.

So the question now. How can I set Buckminster not to look in his "native"
target platform for plugins?

Thanks.


ps By the way, can anyone provide example how "eclipse.platform" reader
works? I've tried such RMAP but couldn't get it to work:

<provider readerType="eclipse.platform"
componentTypes="osgi.bundle,buckminster">
<uri format="plugins/{0}">
<bc:propertyRef key="buckminster.component" />
</uri>
</provider>

------=_Part_4204_11413542.1211813309325
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi.<br><br>I have found strange resolver behaviour when resolving standard PDE plugins.<br><br>1) Created empty target platform with minimal set of plugins (&quot;org.eclipse.osgi&quot;, etc.)<br>2) Switched workspace to this new target platform <br>
3) Created plugin named &quot;org.apache.log4j&quot; (version &quot;1.0.0&quot;) and put it to SVN<br>4) Created RMAP and CQUERY to this materialize this plugin<br>5) Executed CQUERY and got strange&nbsp;&quot;org.apache.log4j&quot; with version &quot;1.2.13&quot; !!!<br>
<br>According to Buckminster log, there was no query to my SVN at all:<br><br>registered serializer org.jabsorb.serializer.impl.RawJSONArraySerializer<br>registered serializer org.jabsorb.serializer.impl.RawJSONObjectSerializer<br>
registered serializer org.jabsorb.serializer.impl.BeanSerializer<br>registered serializer org.jabsorb.serializer.impl.ArraySerializer<br>registered serializer org.jabsorb.serializer.impl.DictionarySerializer<br>registered serializer org.jabsorb.serializer.impl.MapSerializer<br>
registered serializer org.jabsorb.serializer.impl.SetSerializer<br>registered serializer org.jabsorb.serializer.impl.ListSerializer<br>registered serializer org.jabsorb.serializer.impl.DateSerializer<br>registered serializer org.jabsorb.serializer.impl.StringSerializer<br>
registered serializer org.jabsorb.serializer.impl.NumberSerializer<br>registered serializer org.jabsorb.serializer.impl.BooleanSerializer<br>registered serializer org.jabsorb.serializer.impl.PrimitiveSerializer<br>org.apache.log4j:osgi.bundle: Using resolver rmap<br>
Found two entries for component org.eclipse.equinox.registry:osgi.bundle. Version 3.3.0.v20070522 located at C:/Work/go-product/GO/platform/plugins/org.eclipse.equinox.r egistry_3.3.0.v20070522.jar and version 3.3.1.R33x_v20070802 at C:/Work/go-product/GO/platform/plugins/org.eclipse.equinox.r egistry_3.3.1.R33x_v20070802.jar <br>
Found two entries for component org.eclipse.core.expressions:osgi.bundle. Version 3.2.2.r322_v20070109a located at C:/Work/go-product/GO/platform/plugins/org.eclipse.core.expr essions_3.2.2.r322_v20070109a.jar and version 3.3.0.v20070606-0010 at C:/Work/go-product/GO/platform/plugins/org.eclipse.core.expr essions_3.3.0.v20070606-0010.jar <br>
<br>6) Found &quot;org.apache.log4j&quot; with version &quot;1.2.13&quot; in my Eclipse installation target platform.<br>7) Changed&nbsp;&quot;org.apache.log4j&quot; version to &quot;2.0.0&quot; in SVN<br>8) Executed CQUERY and got my plugin from SVN <br>
<br><br>So I can made a conclusion, that Buckminster also searches his &quot;native&quot; target platform (target platform which was used to start Eclipse), and if it finds a match here, which has bigger version than others, it will try to materialize this plugin from &quot;native&quot; platform. As such plugin has no&nbsp;source code (most of the times), there will be nothing materialized to workspace and the whole project will&nbsp;fail to launch. <br>
<br>So the question now. How can I set Buckminster not to look in his &quot;native&quot; target platform for plugins?<br> <br>Thanks.<br><br><br>ps By the way, can anyone provide example how &quot;eclipse.platform&quot; reader works? I&#39;ve tried such RMAP but couldn&#39;t get it to work:<br>
<br> &lt;provider readerType=&quot;eclipse.platform&quot; componentTypes=&quot;osgi.bundle,buckminster&quot;&a mp;gt; <br> &nbsp;&nbsp;&lt;uri format=&quot;plugins/{0}&quot;&gt;<br> &nbsp;&nbsp;&nbsp;&nbsp;&lt;bc:propertyR ef key=&quot;buckminster.component&quot; /&gt;<br>
&nbsp;&nbsp;&lt;/uri&gt;<br> &lt;/provider&gt;<br><br>

------=_Part_4204_11413542.1211813309325--
Previous Topic:Buckminster setpref command missing from latest headless?
Next Topic:Re: [buckminster-dev] Strange resolver behaviour when resolving PDE plugins - using "native&quo
Goto Forum:
  


Current Time: Thu Oct 30 23:48:33 GMT 2014

Powered by FUDForum. Page generated in 0.01480 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software