|
|
|
| Re: JFace dependancies [message #447915 is a reply to message #447907] |
Tue, 21 December 2004 21:08   |
 Benjamin Pasero
Messages: 337
Registered: July 2009 |
Senior Member |
|
|
Thanks Chris, that bug report is exactly what I was talking about.
Too bad that activity froze some months ago :/
Regards,
Ben
> I think you need runtime.jar and osgi.jar but not platform.jar.
>
> JFace depends on some classes in the runtime packages. From what I've
> heard, the Platform UI team (they're responsible for JFace, not the SWT
> team) isn't explicitly designing JFace for standalone SWT app use. I think
> they are not trying to make things very tightly coupled to Eclipse, but at
> the same time they aren't practicing any specific discipline to assure that
> there is zero coupling. So there are instances where the JFace classes
> require some runtime classes (which in turn require some osgi classes). I
> believe the Platform UI team is debating whether to devote time to removing
> these dependencies from JFace.
>
> See:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=49497
>
> -Chris
>
>
> "Benjamin Pasero" <bpasero@rssowl.org> wrote in message
> news:cq9m0j$o84$1@www.eclipse.org...
>
>>Any comments?
>>
>>
>>>Hello,
>>>
>>>I would like to evolve my SWT application with using the Model- and
>>>Viewer-Classes of JFace. Now, as far as I know in order to use JFace I
>>>need to put runtime.jar and platform.jar on the classpath too. I do not
>>>understand why, since the Model-Classes should work without it, or am I
>>>wrong?
>>>
>>>Regards,
>>>Ben
>
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.01599 seconds
Search
Help
Register
Login
Home
