I just realized I don't keep profiler or playground actually checked
out as separate plugin projects ... I would toss them.
On Sep 15, 2005, at 12:47 AM, Greg wrote:
>
> On 15/09/2005, at 2:34 PM, Mike Schrag wrote:
>
>
>>> What is the cycle for testing a plugin under development in
>>> eclipse? I would like to contribute a bit more by sending
>>> patches, instead of just verbal feedback. Do I have to do a full
>>> projects build and install the plugins, or can I just run a
>>> particular plugin via the run or debug buttons? I opened Run...
>>> to create a new target but nothing relating to running a plugin
>>> is listed. What am I missing?
>>>
>>>
>> Any plugin that is in your workspace is available when you
>> Run=>Eclipse Application. This will launch a second eclipse that
>> contains your workspace plugins and has all the typical eclipse
>> goodies like hot code replacement.
>>
>
> Aaaah. Thanks.
>
>
>>
>>
>>
>>> I have just checked out wolips and have followed the instructions
>>> on the wiki for pde development and get the following errors:
>>>
>>>
>> These actually should just be warnings, not errors (yellow hazard
>> icon vs red x icon?). Basically Eclipse in 3.1 added a new access
>> control system on plugins, which in my mind is more annoying than
>> anything. It flags a large number of things as problems that
>> really shouldn't be.
>>
>>
>
> The ones listed in the previous email were errors. There was also
> warnings to the same effect. I am still using 3.1.1 from about a
> month ago. When Uli first sent the email with the links to all the
> packages that were dependent on wolips 2.
>
> Greg
>
>
This archive was generated by hypermail 2.0.0 : Thu Sep 15 2005 - 01:06:52 EDT