[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4185) Simpler load time weaving configuration
[
https://jira.jboss.org/jira/browse/JBIDE-4185?page=com.atlassian.jira.plu...
]
Galder Zamarreño commented on JBIDE-4185:
-----------------------------------------
Hmmmm, actually, having compared user.dir values, I tend to start AS from the server root,
i.e.:
./bin/run.sh and in those cases, the user.dir is:
user.dir: /home/galder/jboss/code/eap/4.3.0.ga.cp04/build/output/jboss-4.3.0.GA_CP04
whereas when I start from JBDS is:
user.dir: /home/galder/jboss/code/eap/4.3.0.ga.cp04/build/output/jboss-4.3.0.GA_CP04/bin
That might be reason why the relative path does not work, cos I need to factor that in
mind and put a ../ before.
Once I get around to testing this again, I'll watch out for this.
Simpler load time weaving configuration
---------------------------------------
Key: JBIDE-4185
URL: https://jira.jboss.org/jira/browse/JBIDE-4185
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: Galder Zamarreño
Assignee: Rob Stryker
Right now, if you wanna use load time weaving, you need to modify
jboss.aop:service=AspectManager
MBean to have EnableLoadtimeWeaving to true and you need to pass the pluggable
instrumentor in
the VM parameters, i.e.
-javaagent:/home/galder/access/eap-rel/4.3.0.ga.cp04/server/279798/deploy/jboss-aop-jdk50.deployer/pluggable-instrumentor.jar
From JBDS, you need to put the full path to this, whereas if running standalone, you can
just do:
JAVA_OPTS="$JAVA_OPTS
-javaagent:server/279798/deploy/jboss-aop-jdk50.deployer/pluggable-instrumentor.jar"
Now, it'd be really helpful if the JBoss AS/EAP server had an option that added did
this (at least the javaagent part)
if load time weaving was enabled (a new option server configuration window (i.e. double
click server name))
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira