Hi Jerry,
Thanks for the sharing your tips. I've done this a slightly different way.
What I do is create a new variable
(Workspace->preferences->Run/Debug->String substitution) for each version of
the enhancer. For example :
name = enhancer-1.0.1
value = -javaagent:${openjpa.repos.loc}/1.0.1/openjpa-1.0.1.jar
Then in my launch configuration all I have to do is add
${enhancer-1.0.1}, or ${enhancer-1.0.2}, . . .
I still have to do it for each run config, but I only have to set up the
variables once for each eclipse workspace.
YMMV
-mike
On Fri, Mar 5, 2010 at 12:15 PM, No1UNo <[email protected]> wrote:
>
> I wanted to share my configuration in case it proves helpful to others.
> Perhaps someone has an even better solution. If so, I'd love to hear it.
>
> I am building in Eclipse 3.5 with Maven 2.2. Class enhancement is
> automatically invoked from Maven using openjpa-maven-plugin 1.0. This
> works
> great for building installable libraries but doesn't help with debugging.
>
> For debugging, OpenJPA enhancement can be invoked from Eclipse by
> specifying
> '-javaagent:eclipse/openjpa.jar' in the 'Run/Debug Settings' menu. This
> must be done for every launch configuration that you wish to debug which
> can
> be an annoying pain. I've simplified slightly by creating a new 'eclipse'
> directory off the project which contains a symbolic link to the desired
> version of OpenJPA.
>
> NOTE: There is a fragile dependency (version sensitivity). If you upgrade
> OpenJPA versions in pom.xml, say from 1.2.1 to 1.2.2, the symbolic link
> MUST
> be updated as well.
> --
> View this message in context:
> http://n2.nabble.com/Runtime-enhancement-during-Eclipse-debugging-tp4682488p4682488.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
