[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ui-dev] Updating JFace version ID
|
JFace is shown in so many APIs and now suppose you depend on a library
that exposes ISelection (e.g. the workbench) and requires 3.10 as the
upper bound and in my custom view code I'm requiring 3.11 then you have
a version conflict that is not resolveable!
Having multiple version in OSGi only really works if the library is
*not* exposed in the API of the user.
Tom
On 10.06.14 16:48, Mickael Istria wrote:
> On 06/10/2014 04:35 PM, Tom Schindl wrote:
>> I still have doubts we should add generics to the current jface library
>> because it will result in a tremendous amount of warnings many projects
>> will not be able to fix for a long time.
>>
>> Wouldn't it be wiser to introduce a JFace2 which also would allow to
>> break the API and e.g. get away with
>> IStructuredContentProvider#getElements(Object inputElement) : Object[]
> Those projects which really don't want warning could just set an
> upper-bound and keep on depending on jface <= 3.10. JFace doesn't seem
> to be a singleton bundle so it shouldn't be an issue.
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets
> <http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> platform-ui-dev mailing list
> platform-ui-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
>
