Re: [jubula-dev] Best practice: How do you debug RC code?

[Zeb Ford-Reitz <Zeb.Ford-Reitz@xxxxxxxxx>]

One possibility (as much of a hack as it is) is to manually copy the 
compiled class files (for example, from the org.eclipse.jubula.rc.common 
project) into the org.eclipse.jubula.rc.rcp_<version>.jar file. Of 
course, you'll need to run the whole maven script in order to perform 
"final" tests and debugging, but you can at least save some time during 
the cycle.

 - Zeb

On 14.12.2011 14:37, Andreas Scharf wrote:
> Hi,
>
> I'm working with the Jubulas source code for some time now. While 
> debugging the client code (of course) is easy as usual, the 
> "code-try-debug" cycle is very hard if I extend the RC code (i.e. code 
> that runs in the AUT). The reason is, that in case I have a change in 
> let's say org.eclipse.jubula.rc.common, I have to execute the whole 
> maven build script to finally get my org.eclipse.jubula.rc.rcp plugin 
> which I can run in my AUT.
>
> I already tried (for debugging purposes only) to not export the 
> required plugins of org.eclipse.jubula.rc.rcp as jar files but to 
> simply load them as plugins in the AUT which is not working because of 
> class loader problems.
>
> So the question is: How does your "code-try-debug" cycle look like? Do 
> you also have to execute the whole maven script all the time?
>
> Best regards,
> Andreas


--
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig

Tel.: +49-531-24330-0
Fax:  +49-531-24330-99
http: www.bredex.de

Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst
Amtsgericht Braunschweig HRB 2450

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature