Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » feature/plugin versions
feature/plugin versions [message #789596] Fri, 03 February 2012 06:49 Go to next message
Eclipse User
Do I have to match plugins version with the feature that include them?

I have a feature with a particular version, say 2, but one of the
included plugins has different version number, say 4.8. Now Buckminster
perform site.p2 action is complaining that the plugin id[2.0.0,2.0.0] is
not known to Buckminster.
The Buckminster commands used here is straightforward, and the
properties file is probably very similar to the one from the examples.

Appreciate any ideas or pointers to where I should look next.
Re: feature/plugin versions [message #789597 is a reply to message #789596] Fri, 03 February 2012 06:51 Go to previous messageGo to next message
Eclipse User
On 2/2/2012 10:49 PM, Abdelhalim Ragab wrote:
> Do I have to match plugins version with the feature that include them?
>
> I have a feature with a particular version, say 2, but one of the
> included plugins has different version number, say 4.8. Now Buckminster
> perform site.p2 action is complaining that the plugin id[2.0.0,2.0.0] is
> not known to Buckminster.
> The Buckminster commands used here is straightforward, and the
> properties file is probably very similar to the one from the examples.
>
> Appreciate any ideas or pointers to where I should look next.

Forgot to mention that this happens in headless mode on a Windows 7
machine, and of course it works fine from the IDE :-)
Re: feature/plugin versions [message #789778 is a reply to message #789597] Fri, 03 February 2012 11:47 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2500
Registered: July 2009
Senior Member
On 2012-03-02 7:51, Abdelhalim Ragab wrote:
> On 2/2/2012 10:49 PM, Abdelhalim Ragab wrote:
>> Do I have to match plugins version with the feature that include them?
>>
yes :)
Since your feature has specified an exact version of 2.0.0 of the
particular plugin, if that is not found, it will naturally not work.
You have to use a range.

>> I have a feature with a particular version, say 2, but one of the
>> included plugins has different version number, say 4.8. Now Buckminster
>> perform site.p2 action is complaining that the plugin id[2.0.0,2.0.0] is
>> not known to Buckminster.
>> The Buckminster commands used here is straightforward, and the
>> properties file is probably very similar to the one from the examples.
>>
>> Appreciate any ideas or pointers to where I should look next.
>
> Forgot to mention that this happens in headless mode on a Windows 7
> machine, and of course it works fine from the IDE :-)
>
Can not really explain what would cause that to work in the IDE (i.e.
why it is not failing). Do you perhaps have a 2.0.0 version of the
plugin available somewhere in the target platform, or installed in the IDE?

Regards
- henrik
Re: feature/plugin versions [message #790026 is a reply to message #789778] Fri, 03 February 2012 18:11 Go to previous messageGo to next message
Eclipse User
On 2/3/2012 3:47 AM, Henrik Lindberg wrote:
>
> On 2012-03-02 7:51, Abdelhalim Ragab wrote:
>> On 2/2/2012 10:49 PM, Abdelhalim Ragab wrote:
>>> Do I have to match plugins version with the feature that include them?
>>>
> yes :)
> Since your feature has specified an exact version of 2.0.0 of the
> particular plugin, if that is not found, it will naturally not work.
> You have to use a range.
May be I wasn't clear on this point. The feature specifies the correct
plugin version, but the feature version itself is different from the
plugin version.


> Can not really explain what would cause that to work in the IDE (i.e.
> why it is not failing). Do you perhaps have a 2.0.0 version of the
> plugin available somewhere in the target platform, or installed in the IDE?
>
As I understand, the IDE is behaving correctly because the feature (v
2.0.0) specifies the plugin version as 4.8.0, and the plugin version
matches that.


> Regards
> - henrik
>
Re: feature/plugin versions [message #790047 is a reply to message #790026] Fri, 03 February 2012 18:54 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2500
Registered: July 2009
Senior Member
On 2012-03-02 19:11, Abdelhalim Ragab wrote:
> On 2/3/2012 3:47 AM, Henrik Lindberg wrote:
>>
>> On 2012-03-02 7:51, Abdelhalim Ragab wrote:
>>> On 2/2/2012 10:49 PM, Abdelhalim Ragab wrote:
>>>> Do I have to match plugins version with the feature that include them?
>>>>
>> yes :)
>> Since your feature has specified an exact version of 2.0.0 of the
>> particular plugin, if that is not found, it will naturally not work.
>> You have to use a range.
> May be I wasn't clear on this point. The feature specifies the correct
> plugin version, but the feature version itself is different from the
> plugin version.
>

huh?

A feature lives a life of its own, and has its own version. Has nothing
to do with the versions of the things it includes. Which I think answers
your original question (which I did not understand at first).


>> Can not really explain what would cause that to work in the IDE (i.e.
>> why it is not failing). Do you perhaps have a 2.0.0 version of the
>> plugin available somewhere in the target platform, or installed in the
>> IDE?
>>
> As I understand, the IDE is behaving correctly because the feature (v
> 2.0.0) specifies the plugin version as 4.8.0, and the plugin version
> matches that.
>
So where exactly does it break when you are running this with headless
Buckminster?

- henrik
Re: feature/plugin versions [message #790053 is a reply to message #790047] Fri, 03 February 2012 19:03 Go to previous messageGo to next message
Eclipse User
On 2/3/2012 10:54 AM, Henrik Lindberg wrote:

>
> A feature lives a life of its own, and has its own version. Has nothing
> to do with the versions of the things it includes. Which I think answers
> your original question (which I did not understand at first).

Yup, this is my understanding as well.


>> As I understand, the IDE is behaving correctly because the feature (v
>> 2.0.0) specifies the plugin version as 4.8.0, and the plugin version
>> matches that.
>>
> So where exactly does it break when you are running this with headless
> Buckminster?

I'm getting the error message from Buckminster perform site.p2 action:
No component named <plugin_id>:osgi.bundle/[2.0.0,2.0.0] is known to
Buckminster


I don't have any version restriction on this particular plugin, and its
version everywhere is 4.8.0

I don't know how/where Buckminster got this 2.0.0 except from the
feature version (Note that other plugins match the feature version, and
they all have v 2.0.0 except this one).

I cannot even find any log or stacktrce that give me any additional info.

Thanks for the help
Re: feature/plugin versions [message #791445 is a reply to message #790053] Sun, 05 February 2012 20:55 Go to previous message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 02/03/2012 08:03 PM, Abdelhalim Ragab wrote:
> I'm getting the error message from Buckminster perform site.p2 action:
> No component named <plugin_id>:osgi.bundle/[2.0.0,2.0.0] is known to Buckminster
>
>
> I don't have any version restriction on this particular plugin, and its version everywhere is 4.8.0
>
Somewhere within your resolution scope, some feature or plug-in adds this restriction. Buckminster normally tells you
the path to the resolution failure at the end of the output.

- thomas
Previous Topic:Git checkout appears to get wrong branch
Next Topic:Need help figuring out how to automate Subclipse build using Buckminster
Goto Forum:
  


Current Time: Fri Oct 31 09:33:04 GMT 2014

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

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