Debugging extensions without deploying as a jar in 9.0.3?

Question

The doc refers to a manual way of installing addins during the debugging phase which I hope removes the need to package the addin as a jar.
'For debugging, and for some other extension types, an alternative manual installation process should be used. Manual installation is described in the section on debugging.'
Does anyone have any details - I couldn't find it in the 'section on debugging'.
Thanks
Mark

Answer 1

One way to do this is to set the compilation output directory of your addin to ${jdev.home}/jdev/classes, then modify the file ${jdev.home}/jdev/lib/addins.xml to include an entry for your addin (see existing contents for examples).
${jdev.home}/jdev/classes is early in JDeveloper's classpath, so classes in this directory will be picked up first.
I usually use remote debugging to debug addins (even when I'm only using one machine). You can configure JDeveloper to listen for the remote debugger by running it like this:
jdev.exe -ojvm -J-XXdebugport4000
(replace 4000 with your preferred port number). Then, in a separate instance of JDeveloper, set up your project for remote debugging and connect to localhost on the port you specified.
Thanks,
Brian
JDev Team