Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Kepler IDE: Error Message Cannot determine filter for requirement to this element
Kepler IDE: Error Message Cannot determine filter for requirement to this element [message #1014516] Tue, 26 February 2013 00:44 Go to next message
Lothar Werzinger is currently offline Lothar WerzingerFriend
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Hi,

I am getting this peculiar error message with buckminster in the Kepler Milestone IDE:
Quote:

[start xxx.product.feature:eclipse.feature$5.0.0.qualifier#site.p2]
publishing result
E Included element xxx.product.feature.feature.group 5.0.0.D-lothar-20130226-0040 is missing. Cannot determine filter for requirement to this element.


if I look into the p2 site created by buckminster to create the product I can see
Quote:

ls /tmp/buckminster/build/xxx.product.feature_5.0.0-eclipse.feature/site.p2/features/xxx.product.feature*
/tmp/buckminster/build/xxx.product.feature_5.0.0-eclipse.feature/site.p2/features/xxx.product.feature_5.0.0.D-lothar-20130226-0040.jar


Searching the web for Cannot determine filter for requirement to this element. together with Buckminster did not yield a single result.

Edit (2013-02-26):
Interestingly the problem only occurs in the IDE (Kepler Milestone) and not if I try to build from Jenkins. As I use the builds in the IDE to verify that the product actually works before I check things in this is a big problem for me right now.

Edit (2-13-03-01):
I double verified that the exact same sources fail reproducibly to build in the Kepler IDE at the site.p2 step but build fine in the Juno IDE. Here's the console log from Juno:

Quote:

[start xxx.feature:eclipse.feature$5.0.0.qualifier#site.p2]
[end xxx.product.feature:eclipse.feature$5.0.0.qualifier#site.p2]
[start xxx.product.feature:eclipse.feature$5.0.0.qualifier#create.product]
[ant] /tmp/eclipse/plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
[ant] file:/tmp/buckminster/build/xxx.product.feature_5.0.0-eclipse.feature/site.p2/
[ant] /tmp/buckminster/build/xxx.product.feature_5.0.0-eclipse.feature/mmt-rcp.gtk.linux.x86_64
[end xxx.product.feature:eclipse.feature$5.0.0.qualifier#create.product]


What is the meaning of this message and how can I fix it?


Thanks in advance!

[Updated on: Sat, 02 March 2013 00:05]

Report message to a moderator

Re: Error message: Cannot determine filter for requirement to this element [message #1014634 is a reply to message #1014516] Tue, 26 February 2013 07:39 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1812
Registered: July 2009
Location: Firenze, Italy
Senior Member
Hi

by googling, it looks like they have a similar problem with tycho: in
that case the problem happens, as far as I understand, when you build
the site of a feature which refers to another feature using the version
with the qualifier...

is that your case?

cheers
Lorenzo

On 02/26/2013 01:44 AM, Lothar Werzinger wrote:
> Hi,
>
> I am getting this peculiar error message with buckminster:
> Quote:
>> publishing result
>> E Included element xxx.product.feature.feature.group
>> 5.0.0.D-lothar-20130226-0040 is missing. Cannot determine filter for
>> requirement to this element.
>
>
> if I look into the p2 site created by buckminster to create the product
> I can see
> Quote:
>> ls
>> /tmp/buckminster/build/xxx.product.feature_5.0.0-eclipse.feature/site.p2/features/xxx.product.feature*
>>
>> /tmp/buckminster/build/xxx.product.feature_5.0.0-eclipse.feature/site.p2/features/xxx.product.feature_5.0.0.D-lothar-20130226-0040.jar
>>
>
>
> Searching the web for Cannot determine filter for requirement to this
> element. together with Buckminster did not yield a single result.
>
> What is the meaning of this message and how can I fix it?
>
> Thanks in advance!


--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it


Re: Error message: Cannot determine filter for requirement to this element [message #1014820 is a reply to message #1014634] Tue, 26 February 2013 14:26 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar WerzingerFriend
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
That is an interesting idea, but not the case here.

Interestingly the problem only occurs in the IDE (Kepler Milestone) and not if I try to build from Jenkins.

Thanks.
Re: Error message: Cannot determine filter for requirement to this element [message #1015048 is a reply to message #1014820] Wed, 27 February 2013 09:48 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1812
Registered: July 2009
Location: Firenze, Italy
Senior Member
On 02/26/2013 03:26 PM, Lothar Werzinger wrote:
> That is an interesting idea, but not the case here.
>
> Interestingly the problem only occurs in the IDE (Kepler Milestone) and
> not if I try to build from Jenkins.
>
> Thanks.

How do you materialize the target platform for your product?

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it


Re: Error message: Cannot determine filter for requirement to this element [message #1015188 is a reply to message #1015048] Wed, 27 February 2013 17:20 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar WerzingerFriend
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
I use a buckminster cquery (the same) in both cases to materialize the TP.
Re: Error message: Cannot determine filter for requirement to this element [message #1015317 is a reply to message #1015188] Thu, 28 February 2013 08:30 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1812
Registered: July 2009
Location: Firenze, Italy
Senior Member
On 02/27/2013 06:20 PM, Lothar Werzinger wrote:
> I use a buckminster cquery (the same) in both cases to materialize the TP.

but in the IDE did you start with an empty target platform? or did you
simply run the materialization?

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it


Re: Error message: Cannot determine filter for requirement to this element [message #1015420 is a reply to message #1015317] Thu, 28 February 2013 14:25 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar WerzingerFriend
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
I started with an empty TP and I made sure that the resulting Buckminster TP after materialization contains only the .buckminster/tp directory as a location, as we have had problems before if the TP after materialization also contained the ${eclipse_home} location that is there by default
Re: Error message: Cannot determine filter for requirement to this element [message #1015679 is a reply to message #1015420] Fri, 01 March 2013 16:38 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1812
Registered: July 2009
Location: Firenze, Italy
Senior Member
On 02/28/2013 03:25 PM, Lothar Werzinger wrote:
> I started with an empty TP and I made sure that the resulting
> Buckminster TP after materialization contains only the .buckminster/tp
> directory as a location, as we have had problems before if the TP after
> materialization also contained the ${eclipse_home} location that is
> there by default

an easier approach is to follow the steps found here

http://wiki.eclipse.org/Extending_or_Contributing_to_Buckminster#Prepare_an_empty_target_platform

however, if you still have problems in the IDE, could you share the
project or is it closed source?

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it


Re: Error message: Cannot determine filter for requirement to this element [message #1015735 is a reply to message #1015679] Sat, 02 March 2013 00:08 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar WerzingerFriend
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Lorenzo Bettini wrote on Fri, 01 March 2013 08:38

an easier approach is to follow the steps found here

http://wiki.eclipse.org/Extending_or_Contributing_to_Buckminster#Prepare_an_empty_target_platform

however, if you still have problems in the IDE, could you share the
project or is it closed source?



That's more or less the same steps I use to create the TP.
Unfortunately I can't share the project.

I double verified that the problem occurs only in the Kepler IDE and not in the Juno IDE.
I updated the original post to reflect that.
Re: Error message: Cannot determine filter for requirement to this element [message #1015753 is a reply to message #1015735] Sat, 02 March 2013 08:48 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1812
Registered: July 2009
Location: Firenze, Italy
Senior Member
On 03/02/2013 01:08 AM, Lothar Werzinger wrote:
> Lorenzo Bettini wrote on Fri, 01 March 2013 08:38
>> an easier approach is to follow the steps found here
>>
>> http://wiki.eclipse.org/Extending_or_Contributing_to_Buckminster#Prepare_an_empty_target_platform
>>
>>
>> however, if you still have problems in the IDE, could you share the
>> project or is it closed source?
>
>
> That's more or less the same steps I use to create the TP.
> Unfortunately I can't share the project.
>
> I double verified that the problem occurs only in the Kepler IDE and not
> in the Juno IDE.
> I updated the original post to reflect that.

Hi

I tried with Kepler myself, and experience exactly the same problem,
with this example

http://sourceforge.net/p/buckyexamples/bucky-mail-rcp/

apparently, running site.p2 action in the IDE on a feature project
containing a product configuration or including a feature which in turns
contains a product configuration (e.g., in the example above, on the
project org.eclipse.buckminster.examples.rcp.mail.product.site) leads to
this error...

the strange thing is that the site.p2 is actually created correctly...

could it be that the installed buckminster is built against Juno?

Thomas?

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it


Re: Error message: Cannot determine filter for requirement to this element [message #1015758 is a reply to message #1015753] Sat, 02 March 2013 10:09 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
I suggest that you enter a bugzilla for this. Mention how to build using
the example so that it succeeds and so that it fails. That will make it
easy to track down. I don't have any good guesses.

- thomas

On 2013-03-02 09:48, Lorenzo Bettini wrote:
> On 03/02/2013 01:08 AM, Lothar Werzinger wrote:
>> Lorenzo Bettini wrote on Fri, 01 March 2013 08:38
>>> an easier approach is to follow the steps found here
>>>
>>> http://wiki.eclipse.org/Extending_or_Contributing_to_Buckminster#Prepare_an_empty_target_platform
>>>
>>>
>>> however, if you still have problems in the IDE, could you share the
>>> project or is it closed source?
>>
>>
>> That's more or less the same steps I use to create the TP.
>> Unfortunately I can't share the project.
>>
>> I double verified that the problem occurs only in the Kepler IDE and not
>> in the Juno IDE.
>> I updated the original post to reflect that.
>
> Hi
>
> I tried with Kepler myself, and experience exactly the same problem,
> with this example
>
> http://sourceforge.net/p/buckyexamples/bucky-mail-rcp/
>
> apparently, running site.p2 action in the IDE on a feature project
> containing a product configuration or including a feature which in turns
> contains a product configuration (e.g., in the example above, on the
> project org.eclipse.buckminster.examples.rcp.mail.product.site) leads to
> this error...
>
> the strange thing is that the site.p2 is actually created correctly...
>
> could it be that the installed buckminster is built against Juno?
>
> Thomas?
>
> cheers
> Lorenzo
>
Re: Error message: Cannot determine filter for requirement to this element [message #1015823 is a reply to message #1015758] Sun, 03 March 2013 09:13 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1812
Registered: July 2009
Location: Firenze, Italy
Senior Member
Done: https://bugs.eclipse.org/bugs/show_bug.cgi?id=402230

hope I provided enough information

cheers
Lorenzo

On 03/02/2013 11:09 AM, Thomas Hallgren wrote:
> I suggest that you enter a bugzilla for this. Mention how to build using
> the example so that it succeeds and so that it fails. That will make it
> easy to track down. I don't have any good guesses.
>
> - thomas
>
> On 2013-03-02 09:48, Lorenzo Bettini wrote:
>> On 03/02/2013 01:08 AM, Lothar Werzinger wrote:
>>> Lorenzo Bettini wrote on Fri, 01 March 2013 08:38
>>>> an easier approach is to follow the steps found here
>>>>
>>>> http://wiki.eclipse.org/Extending_or_Contributing_to_Buckminster#Prepare_an_empty_target_platform
>>>>
>>>>
>>>>
>>>> however, if you still have problems in the IDE, could you share the
>>>> project or is it closed source?
>>>
>>>
>>> That's more or less the same steps I use to create the TP.
>>> Unfortunately I can't share the project.
>>>
>>> I double verified that the problem occurs only in the Kepler IDE and not
>>> in the Juno IDE.
>>> I updated the original post to reflect that.
>>
>> Hi
>>
>> I tried with Kepler myself, and experience exactly the same problem,
>> with this example
>>
>> http://sourceforge.net/p/buckyexamples/bucky-mail-rcp/
>>
>> apparently, running site.p2 action in the IDE on a feature project
>> containing a product configuration or including a feature which in turns
>> contains a product configuration (e.g., in the example above, on the
>> project org.eclipse.buckminster.examples.rcp.mail.product.site) leads to
>> this error...
>>
>> the strange thing is that the site.p2 is actually created correctly...
>>
>> could it be that the installed buckminster is built against Juno?
>>
>> Thomas?
>>
>> cheers
>> Lorenzo
>>
>


--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it


Re: Error message: Cannot determine filter for requirement to this element [message #1016055 is a reply to message #1015823] Mon, 04 March 2013 18:27 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar WerzingerFriend
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Lorenzo Bettini wrote on Sun, 03 March 2013 01:13
Done: https://bugs.eclipse.org/bugs/show_bug.cgi?id=402230

hope I provided enough information

cheers
Lorenzo



Thanks for creating the bug. It's good to know that someone else was able to recreate the issue.
Re: Error message: Cannot determine filter for requirement to this element [message #1105028 is a reply to message #1016055] Mon, 09 September 2013 08:42 Go to previous messageGo to next message
Matthew Webber is currently offline Matthew WebberFriend
Messages: 198
Registered: December 2010
Senior Member
I have also hit the bug. This is with the latest version of Buckminster in Kepler, so it looks like the fix is incomplete.
Re: Error message: Cannot determine filter for requirement to this element [message #1258539 is a reply to message #1105028] Thu, 27 February 2014 13:39 Go to previous message
Victor Roldan Betancort is currently offline Victor Roldan BetancortFriend
Messages: 524
Registered: July 2009
Senior Member
Hi guys,

I actually hit this one. For some weird reason I could not find bucky in the Kepler Simultaneous Release P2 site, so went to the bucky eclipse.org download page (http://www.eclipse.org/buckminster/downloads.html) which seems not updated, so I ended up using 1.5.0 on my Kepler 4.3.1 workbench, which lead to this issue.

I found this bug, uninstalled bucky 1.5.0, and finally found the 1.6.0 release published at http://download.eclipse.org/tools/buckminster/updates-4.3, and everything worked.

It's weird because this issue did not use to happen in our jenkins/bucky 4.2 CI machine.

Also don't forget to clear .metadata/org.eclipse.buckminster.core cache from time to time, specially when switching versions. I actually had a whole lot of different issues due to inconsistent data in that folder.

Best Regards,
Víctor Roldán [Open Canarias]
Previous Topic:Version rejected during materialisation / possible qualifier problem
Next Topic:buckminster emma feature
Goto Forum:
  


Current Time: Fri Apr 26 05:13:21 GMT 2024

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

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

Back to the top