On 30/03/2008, at 9:27 PM, Lachlan Deck wrote:
> On 30/03/2008, at 8:27 PM, Q wrote:
>>
>> On 30/03/2008, at 5:48 PM, Andrew Lindesay wrote:
>>> Hello;
>>>
>>> I'm wondering if there any way to work on the wolips plugins with
>>> a debugger? I can imagine it is a bit tricky because one is
>>> "editing with what is being developed", but if there is a way to
>>> get a debugger on it, I'd appreciate knowing about it as it would
>>> probably be much faster.
>>
>> You should be using the plugin(s) you are working on within eclipse
>> as individual projects and launching using Run As Eclipse
>> Application. This will cause eclipse to launch a second instance of
>> eclipse with a new workspace that you can then debug, modify with
>> hot replace and step through as necessary.
>
> So if you're making changes to, for example,
> org.objectstyle.wolips.eomodeler,
> org.objectstyle.wolips.eomodeler.core,
> org.objecstyle.wolips.baseforplugins
>
> What do you choose to run in order to simulate running Eclipse/
> WOLips as normal?
>
> e.g., creating a new EOModel + opening it and seeing if prototypes
> are available?
Okay, that's easy enough... cool. Thanks Quinton.
Is there some standard logging in place (ala log4j etc)?
with regards,
--Lachlan Deck
This archive was generated by hypermail 2.0.0 : Sun Mar 30 2008 - 06:56:36 EDT