You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Cristiano Gavião <cv...@gmail.com> on 2017/03/04 18:58:40 UTC
GoGo 1.x doesn't work with equinox
Hello,
Eclipse Equinox have been using GoGo since version 3.8 (I think it is
Juno) and since that they do not upgrade gogo version (0.8.0).
But even Eclipse team do not upgrading gogo's version, to use newer
versions was just a simple matter to deploy the new bundles into the
container and enjoy (until GoGo version 0.16.4).
Today I decided to try the latest gogo version (1.0.2) and sadly it was
not possible this time.
Further investigation shows me that *org.eclipse.equinox.console* has
this import: org.apache.felix.service.command;*/status=provisional/*,
but new gogo version do not exports that anymore.
Could someone explain me why was this status=provisional added anyway ?
regards,
Cristiano
Re: GoGo 1.x doesn't work with equinox
Posted by Raymond Auge <ra...@liferay.com>.
On Fri, Mar 10, 2017 at 4:08 PM, Cristiano Gavião <cv...@gmail.com>
wrote:
> Hi Ray,
>
> understood ! thanks for the explanation !
>
> btw, do you think that worth to open a request to Equinox to move to GoGo
> 1.x ?
>
Probably a good idea!
- Ray
> regards,
>
>
> Cristiano
>
>
>
> On 04/03/2017 18:34, Raymond Auge wrote:
>
>> At one point the gogo shell was subject of an OSGi RFP attempting to
>> create
>> a shell specification. During that time and according the Apache Felix's
>> policy on consuming and implementing OSGi API, the packages of the
>> in-progress project in felix used the org.apache.felix namespace and were
>> marked provisional as you have noticed.
>>
>> Fast forward several years and the shell specification never progressed
>> any
>> further. However gogo did, still having the provisional attribute on it's
>> packages.
>>
>> Moving further forward to late 2016 when some fairly significant work was
>> done to gogo and finally it was decided that after almost a decade gogo
>> should become finally version 1.0.0 and at that time since an OSGi spec
>> was
>> now far from likely the attribute provisional was dropped.
>>
>> The provisional attribute is merely a hint to developers to be aware that
>> the API they are consuming is likely to be subject to change, more so than
>> in pure semantic ways. It could suddenly become incompatible with no
>> explanation because the design is not yet finalized.
>>
>> I hope this helps explain things. :)
>>
>> - Ray
>>
>>
>> On Sat, Mar 4, 2017 at 1:58 PM, Cristiano Gavião <cv...@gmail.com>
>> wrote:
>>
>> Hello,
>>>
>>> Eclipse Equinox have been using GoGo since version 3.8 (I think it is
>>> Juno) and since that they do not upgrade gogo version (0.8.0).
>>>
>>> But even Eclipse team do not upgrading gogo's version, to use newer
>>> versions was just a simple matter to deploy the new bundles into the
>>> container and enjoy (until GoGo version 0.16.4).
>>>
>>> Today I decided to try the latest gogo version (1.0.2) and sadly it was
>>> not possible this time.
>>>
>>> Further investigation shows me that *org.eclipse.equinox.console* has
>>> this
>>> import: org.apache.felix.service.command;*/status=provisional/*, but new
>>> gogo version do not exports that anymore.
>>>
>>>
>>> Could someone explain me why was this status=provisional added anyway ?
>>>
>>>
>>> regards,
>>>
>>> Cristiano
>>>
>>>
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
--
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
(@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
(@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
Re: GoGo 1.x doesn't work with equinox
Posted by Cristiano Gavião <cv...@gmail.com>.
Hi Ray,
understood ! thanks for the explanation !
btw, do you think that worth to open a request to Equinox to move to
GoGo 1.x ?
regards,
Cristiano
On 04/03/2017 18:34, Raymond Auge wrote:
> At one point the gogo shell was subject of an OSGi RFP attempting to create
> a shell specification. During that time and according the Apache Felix's
> policy on consuming and implementing OSGi API, the packages of the
> in-progress project in felix used the org.apache.felix namespace and were
> marked provisional as you have noticed.
>
> Fast forward several years and the shell specification never progressed any
> further. However gogo did, still having the provisional attribute on it's
> packages.
>
> Moving further forward to late 2016 when some fairly significant work was
> done to gogo and finally it was decided that after almost a decade gogo
> should become finally version 1.0.0 and at that time since an OSGi spec was
> now far from likely the attribute provisional was dropped.
>
> The provisional attribute is merely a hint to developers to be aware that
> the API they are consuming is likely to be subject to change, more so than
> in pure semantic ways. It could suddenly become incompatible with no
> explanation because the design is not yet finalized.
>
> I hope this helps explain things. :)
>
> - Ray
>
>
> On Sat, Mar 4, 2017 at 1:58 PM, Cristiano Gavi�o <cv...@gmail.com> wrote:
>
>> Hello,
>>
>> Eclipse Equinox have been using GoGo since version 3.8 (I think it is
>> Juno) and since that they do not upgrade gogo version (0.8.0).
>>
>> But even Eclipse team do not upgrading gogo's version, to use newer
>> versions was just a simple matter to deploy the new bundles into the
>> container and enjoy (until GoGo version 0.16.4).
>>
>> Today I decided to try the latest gogo version (1.0.2) and sadly it was
>> not possible this time.
>>
>> Further investigation shows me that *org.eclipse.equinox.console* has this
>> import: org.apache.felix.service.command;*/status=provisional/*, but new
>> gogo version do not exports that anymore.
>>
>>
>> Could someone explain me why was this status=provisional added anyway ?
>>
>>
>> regards,
>>
>> Cristiano
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: GoGo 1.x doesn't work with equinox
Posted by Raymond Auge <ra...@liferay.com>.
At one point the gogo shell was subject of an OSGi RFP attempting to create
a shell specification. During that time and according the Apache Felix's
policy on consuming and implementing OSGi API, the packages of the
in-progress project in felix used the org.apache.felix namespace and were
marked provisional as you have noticed.
Fast forward several years and the shell specification never progressed any
further. However gogo did, still having the provisional attribute on it's
packages.
Moving further forward to late 2016 when some fairly significant work was
done to gogo and finally it was decided that after almost a decade gogo
should become finally version 1.0.0 and at that time since an OSGi spec was
now far from likely the attribute provisional was dropped.
The provisional attribute is merely a hint to developers to be aware that
the API they are consuming is likely to be subject to change, more so than
in pure semantic ways. It could suddenly become incompatible with no
explanation because the design is not yet finalized.
I hope this helps explain things. :)
- Ray
On Sat, Mar 4, 2017 at 1:58 PM, Cristiano Gavião <cv...@gmail.com> wrote:
> Hello,
>
> Eclipse Equinox have been using GoGo since version 3.8 (I think it is
> Juno) and since that they do not upgrade gogo version (0.8.0).
>
> But even Eclipse team do not upgrading gogo's version, to use newer
> versions was just a simple matter to deploy the new bundles into the
> container and enjoy (until GoGo version 0.16.4).
>
> Today I decided to try the latest gogo version (1.0.2) and sadly it was
> not possible this time.
>
> Further investigation shows me that *org.eclipse.equinox.console* has this
> import: org.apache.felix.service.command;*/status=provisional/*, but new
> gogo version do not exports that anymore.
>
>
> Could someone explain me why was this status=provisional added anyway ?
>
>
> regards,
>
> Cristiano
>
>
>
--
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
(@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
(@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)