Refiling issue from appengine issue tracker to here:
https://code.google.com/p/googleappengine/issues/detail?id=4122
Original Description:
I work for Zeroturnaround and am trying to integrate the JRebel Eclipse plug-in
with Google Plugin for Eclipse (launch configuration).
Our integration with launch configs usually means adding a JRebel tab to the
launch configuration. This tab modifies the JVM arguments (such as -javaagent:
) to point to JRebel agent.
Adding it to a configuration works, but when opening an existing configuration,
it is apparent that the GAE support removes all -javaagent: arguments or
replaces them with one pointing to the GAE agent. So the JRebel settings (or
even any other manually entered -javaagent settings) will be persisted only
until you open the configuration again.
My suggestion is that GAE support in Eclipse should only look for those
-javaagent: arguments that actually point to GAE and leave any others alone
(this problem also exists when GWT is used without GAE).
Dec 6, 2010
----------
Patch to keep non-GAE projects from being affected:
https://code.google.com/p/google-plugin-for-eclipse/issues/detail?id=54
Original issue reported on code.google.com by joshu...@google.com on 14 Aug 2014 at 5:38
Original issue reported on code.google.com by
joshu...@google.comon 14 Aug 2014 at 5:38