It's depended on because Eclipse people have a sort of obnoxious
behavior of creating really useful classes buried inside various
plugins that they don't move out to more general places even though
the implementations are general. In <3.3, this didn't really matter
because all the plugins shipped in the build, so who cared.
Obviously in 3.3 they are now shipping subsets of plugins, breaking
dependencies like this one.
On Jul 3, 2007, at 5:49 AM, Anders Peterson wrote:
> The Classic download also works. Is this dependency necessary? It
> seems odd to me that a compiled and packaged plugin depends on the
> plugin development environment.
>
> /Anders
>
> Mike Schrag wrote:
>> Use Eclipse for RCP/Plugin Developers
>> On Jul 2, 2007, at 10:10 AM, Anders Peterson wrote:
>>> I downloaded the Eclipse IDE for Java Developers and then
>>> proceeded to install
>>>
>>> http://webobjects.mdimension.com/wolips/nightly/
>>>
>>> (Standard Install only) and got
>>>
>>> WOLips (3.3.4143) requires plug-in "org.eclipse.pde.ui".
>>>
>>> /Anders
>>>
>>> Mike Schrag wrote:
>>>> Same instructions as before, just using 3.3 instead of 3.2.
>>>> ms
>>>> On Jun 29, 2007, at 4:29 PM, Riccardo De Menna wrote:
>>>>>> However, there are five options:
>>>>>> 1-Java Developers
>>>>>> 2-Java EE Developers
>>>>>> 3-C/C++ Developers
>>>>>> 4-RCP/Plugin Developers
>>>>>> 5-Eclipse Classic
>>>>>
>>>>> I say answer number 1...
>>>>>
>>>>> BTW... I know we shouldn't be doing it but you can't really
>>>>> show the candies to the kids and pretend them to ignore the
>>>>> nice basket on the table.
>>>>> So... if we promise not to come here bitching about Europa
>>>>> formatting our drive, can someone post a few easy guidelines to
>>>>> try it?
>>>>>
>>>>> Cheers,
>>>>> Ric
>>>>>
>>>
>
This archive was generated by hypermail 2.0.0 : Tue Jul 03 2007 - 09:07:46 EDT