Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Unable to materialize components in Eclipse 3.7
Unable to materialize components in Eclipse 3.7 [message #835705] Tue, 03 April 2012 11:17 Go to next message
Alex Kravets is currently offline Alex Kravets
Messages: 374
Registered: November 2009
Senior Member
Hello,

I am trying to migrate from Eclipse 3.5 to Eclipse 3.7. To do this I created target definition and trying to materialize the same cquery I used in 3.5, but it fails to find org.apache.lucene.source bundle:

W [0051] : Component request org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617] is in conflict with request org.apache.lucene.source:osgi.bundle/[2.9.1.v201101211721,2.9.1.v201101211721]
W [0051] : Component request org.apache.lucene:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617] is in conflict with request org.apache.lucene:osgi.bundle/[2.9.1.v201101211721,2.9.1.v201101211721]
W [0127] : Component request org.junit.source:osgi.bundle/[3.8.2.v3_8_2_v20100427-1100,3.8.2.v3_8_2_v20100427-1100] is in conflict with request org.junit.source:osgi.bundle/[4.8.2.v4_8_2_v20110321-1705,4.8.2.v4_8_2_v20110321-1705]
W [0127] : Component request org.junit:osgi.bundle/[4.8.2.v4_8_2_v20110321-1705,4.8.2.v4_8_2_v20110321-1705] is in conflict with request org.junit:osgi.bundle/[3.8.2.v3_8_2_v20100427-1100,3.8.2.v3_8_2_v20100427-1100]
E [0051] : No suitable provider for component org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617] was found in searchPath indigo
E   [0051] : Rejecting provider p2(http://download.eclipse.org/releases/indigo?importType=binary[http://download.eclipse.org/releases/indigo?importType=binary]): No component match was found
E [0051] : No suitable provider for component org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617] was found in searchPath galileo
E   [0051] : Rejecting provider p2(http://download.eclipse.org/releases/galileo?importType=binary[http://download.eclipse.org/releases/galileo?importType=binary]): No component match was found


This is my target definition

I also found this information in Incompatibilities between Eclipse 3.6 and 3.7 and I wonder if this has anything to do with it.

What's interesting is that looking at target's bundles I see no source bundle for o.a.lucene v1.9.1, but there is one for v2.9.1:

http://i.imgur.com/2B3A9.png

Lastly, how can I find out with all my plugins and their dependencies who is depending on particular version of a plugin, in this case org.apache.lucene.source?

Thanks,
Alex

[Updated on: Tue, 03 April 2012 21:37]

Report message to a moderator

Re: Unable to materialize components in Eclipse 3.7 [message #835726 is a reply to message #835705] Tue, 03 April 2012 11:48 Go to previous messageGo to next message
Alex Kravets is currently offline Alex Kravets
Messages: 374
Registered: November 2009
Senior Member
Using PDE Dependency Visualization I found which plugin depends on org.apache.lucene - http://i.imgur.com/Lx3G2.png.

However, going through these plugins I don't see anything that depends on org.apache.lucene.source.
Re: Unable to materialize components in Eclipse 3.7 [message #835882 is a reply to message #835726] Tue, 03 April 2012 16:06 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3215
Registered: July 2009
Senior Member
Hi Alex,

Starting with 3.6, an optional dependency to a source bundle is generated automatically when you resolve from the IDE.
Normally that shouldn't cause any problems even when the source is unavailable. In your setup this is apparently
combined with a conflict:

org.apache.lucene:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617] is in conflict with request
org.apache.lucene:osgi.bundle/[2.9.1.v201101211721,2.9.1.v201101211721]

which somehow manifests itself as an error on the optional source bundle. That shouldn't happen and must be considered a
bug. I would appreciate if you could enter a bugzilla for that.

You can turn the new IDE behavior off by setting the property buckminster.download.source to false. Easiest place to do
that is perhaps in the Preferences -> Run/Debug -> String substitution (values entered there are treated as valid
properties during resolution).

- thomas


On 04/03/2012 05:48 PM, Alex Kravets wrote:
> Using PDE Dependency Visualization I found which plugin depends on org.apache.lucene - http://i.imgur.com/Lx3G2.png.
>
> However, going through these plugins I don't see anything that depends on org.apache.lucene.source.
Re: Unable to materialize components in Eclipse 3.7 [message #835918 is a reply to message #835882] Tue, 03 April 2012 17:11 Go to previous messageGo to next message
Alex Kravets is currently offline Alex Kravets
Messages: 374
Registered: November 2009
Senior Member
Thanks Thomas,

Indeed when I removed dependencies on org.eclipse.datatools.sqldevtools.sqlbuilder.feature and org.eclipse.datatools.sqldevtools.feature I was able to materialize from CQUERY, but once it's time to build my product I needed these two features back.

I tried your suggestion, but it did not work. I also tried setting property in my CQUERY:

<cq:property key="buckminster.download.source" value="false"/>


but it still tries to download sources for bundles.

Here is a screenshot just in case I misunderstood something.

Alex

[Updated on: Tue, 03 April 2012 21:37]

Report message to a moderator

Re: Unable to materialize components in Eclipse 3.7 [message #836102 is a reply to message #835918] Wed, 04 April 2012 00:13 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3215
Registered: July 2009
Senior Member
Hi Alex,

That's very odd. Any synthesized source requirement is generated with the filter "(buckminster.download.source=true)"
and should be inactivated with your settings (both ways of doing it are correct). This suggests that there are other
dependencies somewhere that points to the failing source bundle. What's the last component listed in the TAG 0113,
TAG0115, and TAG0117 entries?

- thomas

On 04/03/2012 11:11 PM, Alex Kravets wrote:
> Thanks Thomas,
>
> Indeed when I removed dependencies on org.eclipse.datatools.sqldevtools.sqlbuilder.feature and
> org.eclipse.datatools.sqldevtools.feature I was able to materialize from CQUERY, but once it's time to build my product
> I needed these two features back.
>
> I tried your suggestion, but it did not work. I also tried setting property in my CQUERY:
>
>
> <cq:property key="buckminster.download.source" value="false"/>
>
>
> but it still tries to download sources for bundles.
>
> Here is a http://i.imgur.com/PPrpL.png just in case I didn't misunderstood something.
>
> Alex
Re: Unable to materialize components in Eclipse 3.7 [message #836475 is a reply to message #836102] Wed, 04 April 2012 10:25 Go to previous messageGo to next message
Alex Kravets is currently offline Alex Kravets
Messages: 374
Registered: November 2009
Senior Member
Thomas,

Here is my CQUERY:

<?xml version="1.0" encoding="UTF-8"?>
<cq:componentQuery xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0" resourceMap="../../pluto.rmap">
    <cq:rootRequest name="com.iwaysoftware.integration.tools.build.feature" componentType="eclipse.feature"/>
    <cq:property key="buckminster.download.source" value="false"/>
    <cq:advisorNode namePattern="^com\.iwaysoftware\.integration\.tools\.p2\.feature$" branchTagPath="indigo.build"/>
    <cq:advisorNode namePattern="^com\.iwaysoftware\.integration\.tools\.product\.feature$" branchTagPath="indigo.build"/>
    <cq:advisorNode namePattern="^com\.iwaysoftware\.designer\.ui$" branchTagPath="indigo.build"/>
    <cq:advisorNode namePattern="^org\.eclipse\.emf\.ecore\.nl1$" branchTagPath="i18n"/>
</cq:componentQuery>


And here is the console log during the failure:

org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617]: Rejecting provider p2(http://download.eclipse.org/releases/indigo?importType=binary[http://download.eclipse.org/releases/indigo?importType=binary]): No component match was found
org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617]: No provider was found that could resolve the request
org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617]: Using search path galileo
org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617]: Trying provider p2(http://download.eclipse.org/releases/galileo?importType=binary[http://download.eclipse.org/releases/galileo?importType=binary])
org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617]: Rejecting provider p2(http://download.eclipse.org/releases/galileo?importType=binary[http://download.eclipse.org/releases/galileo?importType=binary]): No component match was found
org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617]: No provider was found that could resolve the request
ERROR   [0136] : No suitable provider for component org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617] was found in resourceMap file:/home/akravets/dev/workspaces/build-3.7/com.iwaysoftware.integration.tools.build.feature/pluto.rmap
  ERROR   [0136] : No suitable provider for component org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617] was found in searchPath indigo
    ERROR   [0136] : Rejecting provider p2(http://download.eclipse.org/releases/indigo?importType=binary[http://download.eclipse.org/releases/indigo?importType=binary]): No component match was found
  ERROR   [0136] : No suitable provider for component org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617] was found in searchPath galileo
    ERROR   [0136] : Rejecting provider p2(http://download.eclipse.org/releases/galileo?importType=binary[http://download.eclipse.org/releases/galileo?importType=binary]): No component match was found
Errors and Warnings
W [0119] : Component request org.junit.source:osgi.bundle/[3.8.2.v3_8_2_v20100427-1100,3.8.2.v3_8_2_v20100427-1100] is in conflict with request org.junit.source:osgi.bundle/[4.8.2.v4_8_2_v20110321-1705,4.8.2.v4_8_2_v20110321-1705]
W [0122] : Component request org.junit:osgi.bundle/[4.8.2.v4_8_2_v20110321-1705,4.8.2.v4_8_2_v20110321-1705] is in conflict with request org.junit:osgi.bundle/[3.8.2.v3_8_2_v20100427-1100,3.8.2.v3_8_2_v20100427-1100]
W [0121] : Component request org.apache.lucene:osgi.bundle/[2.9.1.v201101211721,2.9.1.v201101211721] is in conflict with request org.apache.lucene:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617]
W [0121] : Component request org.apache.lucene.source:osgi.bundle/[2.9.1.v201101211721,2.9.1.v201101211721] is in conflict with request org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617]
W [0121] : Component request org.apache.lucene:osgi.bundle/[2.9.1.v201101211721,2.9.1.v201101211721] is in conflict with request org.apache.lucene:osgi.bundle/[1.9.0,2.0.0)
E [0136] : No suitable provider for component org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617] was found in searchPath indigo
E   [0136] : Rejecting provider p2(http://download.eclipse.org/releases/indigo?importType=binary[http://download.eclipse.org/releases/indigo?importType=binary]): No component match was found
E [0136] : No suitable provider for component org.apache.lucene.source:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617] was found in searchPath galileo
E   [0136] : Rejecting provider p2(http://download.eclipse.org/releases/galileo?importType=binary[http://download.eclipse.org/releases/galileo?importType=binary]): No component match was found
TAG-ID 0119 = Query for com.iwaysoftware.integration.tools.build.feature:eclipse.feature, path: com.iwaysoftware.integration.tools.build.feature:eclipse.feature$0.1.0.qualifier -> com.iwaysoftware.integration.tools.product.feature:eclipse.feature$0.1.0.qualifier -> com.iwaysoftware.integration.tools.p2.feature:eclipse.feature$0.1.0.qualifier -> org.eclipse.sdk:eclipse.feature$3.7.2.r37x_v20111213-7Q7xALDPb32vCjY6UACVPdFTz-icPtJkUadz0lMmk4z-8 -> org.eclipse.jdt.source:eclipse.feature$3.7.2.v20120120-1414-7z8gFcuFMP7BW5XTz0jLTnz0l9B1
TAG-ID 0121 = Query for com.iwaysoftware.integration.tools.build.feature:eclipse.feature, path: com.iwaysoftware.integration.tools.build.feature:eclipse.feature$0.1.0.qualifier -> com.iwaysoftware.integration.tools.product.feature:eclipse.feature$0.1.0.qualifier -> com.iwaysoftware.integration.tools.p2.feature:eclipse.feature$0.1.0.qualifier -> org.eclipse.sdk:eclipse.feature$3.7.2.r37x_v20111213-7Q7xALDPb32vCjY6UACVPdFTz-icPtJkUadz0lMmk4z-8 -> org.eclipse.help:eclipse.feature$1.3.0.v20110530-0844-7i7uFFmFFl8nvqbDpEqTvx
TAG-ID 0122 = Query for com.iwaysoftware.integration.tools.build.feature:eclipse.feature, path: com.iwaysoftware.integration.tools.build.feature:eclipse.feature$0.1.0.qualifier -> com.iwaysoftware.integration.tools.product.feature:eclipse.feature$0.1.0.qualifier -> com.iwaysoftware.integration.tools.p2.feature:eclipse.feature$0.1.0.qualifier -> org.eclipse.sdk:eclipse.feature$3.7.2.r37x_v20111213-7Q7xALDPb32vCjY6UACVPdFTz-icPtJkUadz0lMmk4z-8 -> org.eclipse.jdt:eclipse.feature$3.7.2.v20120120-1414-7z8gFcuFMP7BW5XTz0jLTnz0l9B1
TAG-ID 0136 = Query for com.iwaysoftware.integration.tools.build.feature:eclipse.feature, path: com.iwaysoftware.integration.tools.build.feature:eclipse.feature$0.1.0.qualifier -> com.iwaysoftware.integration.tools.product.feature:eclipse.feature$0.1.0.qualifier -> com.iwaysoftware.integration.tools.p2.feature:eclipse.feature$0.1.0.qualifier -> org.eclipse.datatools.sqldevtools.feature:eclipse.feature$1.9.2.v201109161655-7N847OFDsn3ivl-o7D-5qe3gjF1Q -> org.eclipse.datatools.sqldevtools.results.feature:eclipse.feature$1.9.2.v201109161655-57B6AkF7BD7ICHBKCS


Thanks,
Alex
Re: Unable to materialize components in Eclipse 3.7 [message #873645 is a reply to message #836475] Fri, 18 May 2012 14:46 Go to previous messageGo to next message
Alex Kravets is currently offline Alex Kravets
Messages: 374
Registered: November 2009
Senior Member
I am still having issues with materializing in 3.7. However, this time I am having problems using Eclipse 3.7 with Buckminster 3.7 materializing using 3.5 target platform. When I materialize I get errors about not being able to find source for org.apache.batik.xml.source, in target platform I see org.apache.batik at version 1.6.0 and org.apache.batik.source at version 1.7.0. I tried using same target definition and setup in Eclipse 3.5 and everything works fine. I also tried as suggested to use buckminster.download.source=true in 3.7. Here is what's interesting, on some tried I was successful in materializing in 3.7, but I don't know under what circumstances it was successful.

So, is there a bug in Buckminster 3.7 where buckminster.download.source=true is not honored, or some other issue? Has anybody seen the problems I am having?

Thanks,
Alex
Re: Unable to materialize components in Eclipse 3.7 [message #874657 is a reply to message #873645] Mon, 21 May 2012 06:22 Go to previous messageGo to next message
Matthew Webber is currently offline Matthew Webber
Messages: 198
Registered: December 2010
Senior Member
>> So, is there a bug in Buckminster 3.7 where buckminster.download.source=true is not honored, or some other issue?

I did have a problem with buckminster.download.source in 3.7, and the problem turned out to be a bug in property handling (not specific to buckminster.download.source). The bug occurs when you have advisor nodes, which I don't think it applies to your case, but anyhow:

The bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=370928
Background: http://www.eclipse.org/forums/index.php/mv/msg/262059/756620/#msg_756620

Matthew


Re: Unable to materialize components in Eclipse 3.7 [message #892796 is a reply to message #874657] Fri, 29 June 2012 13:53 Go to previous messageGo to next message
Alex Kravets is currently offline Alex Kravets
Messages: 374
Registered: November 2009
Senior Member
I came back to this issue and tried couple of things.

I tried adding this property to providers in RMAP, but this did not resolve the issue.
<property key="buckminster.downlaod.source" value="false"/>

What did work is adding advisor node in CQUERY
<cq:advisorNode namePattern="^.*\.source$" skipComponent="true"/>

I did try to add buckminster.download.source property to cquery initially, but failed to try advisorNode.

Also tried this and Eclipse Juno and it works.

[Updated on: Fri, 29 June 2012 14:04]

Report message to a moderator

Re: Unable to materialize components in Eclipse 3.7 [message #893204 is a reply to message #892796] Tue, 03 July 2012 04:08 Go to previous messageGo to next message
Matthew Webber is currently offline Matthew Webber
Messages: 198
Registered: December 2010
Senior Member
If this is an accurate cut and paste:
Quote:
<property key="buckminster.downlaod.source" value="false"/>

then there is a spelling error there: downlaod rather than download.

Matthew

Re: Unable to materialize components in Eclipse 3.7 [message #901073 is a reply to message #893204] Thu, 09 August 2012 11:41 Go to previous message
Alex Kravets is currently offline Alex Kravets
Messages: 374
Registered: November 2009
Senior Member
Matthew Webber wrote on Tue, 03 July 2012 04:08
If this is an accurate cut and paste:
Quote:
<property key="buckminster.downlaod.source" value="false"/>

then there is a spelling error there: downlaod rather than download.

Matthew



Could be, but in original cquery (http://www.eclipse.org/forums/index.php/mv/msg/322156/836475/#msg_836475) I did spell it correctly and in later post just typed it out. Would've been embarrassing if this didn't work due to me not catching spelling error.
Previous Topic:Procedure to create Fragment project and build using Buckminster
Next Topic:buckminster site.p2 failing juno
Goto Forum:
  


Current Time: Sat Aug 02 00:32:17 EDT 2014

Powered by FUDForum. Page generated in 0.05070 seconds