-
1. Re: @BMRule.targetLocation
adinn Feb 13, 2012 10:27 AM (in response to flavia.rainone)Hi Flavia,
Flavia Rainone wrote:
Is there a way of using AFTER INVOKE with targetLocation?
This is a known issue which was raised and then fixed in Byteman 2.0.0 by James 'Doc' Livingston. If you upgrade to this release you should be able to specify targetLocation="INVOKE foo", targetLocation="AT INVOKE foo" or targetLocation="AFTER INVOKE foo". The preferred format is to include either AT or AFTER as appropriate but we decided to retain the use wihtout AT for backwards compatibility.
-
2. Re: @BMRule.targetLocation
flavia.rainone Feb 13, 2012 12:57 PM (in response to adinn)Ooops, time to upgrade to 2.0.0 then.
Thank you for you quick answer, Andrew.
-
3. Re: @BMRule.targetLocation
flavia.rainone Feb 14, 2012 11:37 AM (in response to flavia.rainone)Upgrading to 2.0.0 did not work. After some digging, I figured the targetLocation was being added to the script (at BMRunnerUtil), without any separator. My test started working after I added a separator to the script:
https://github.com/fl4via/byteman/commit/fe3c5a02a4081745e3809db4b8de25a2d1591c37
Is that correct? Should I create a Jira and submit my commit with a pull request?
-
4. Re: @BMRule.targetLocation
adinn Feb 14, 2012 11:45 AM (in response to flavia.rainone)Hi Flavia,
!"£$%^&*!!!
Flavia Rainone wrote:
Yes, please :-)