Affects Version/s: 5.5.1
Fix Version/s: None
Linux 3.0.0-14-virtual #23-Ubuntu SMP Mon Nov 21 21:09:11 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
I think I found a bug in the the bin/activemq script. It's simple to
fix, and looks like someone was just trying to be too careful.
When trying to determine the Active MQ installation dir, it does this:
...then later it does this:
In my case, I call the script from my home directory, and then when it
tries to <import resource="jetty.xml"/>, it fails because there is no
jetty.xml in my home directory.
I changed the script to do this:
...and now it works perfectly.
That saveddir variable is actually not needed at all. When you call a
script that has "#!/bin/sh" as the 1st line, it invokes a new shell,
so after the script finishes, that shell is closed and you go back to
the calling shell, and cd was never called there.