You need to refresh the bundle that actually uses the new code. As it's not aware of a bundle update it keeps the old references.
Regards, Achim sent from mobile device Am 28.10.2015 6:36 nachm. schrieb "asookazian2" <[email protected]>: > Eclipse Kepler SR1 > Karaf 3.0.3 > > I have a feature with a few bundles that are already installed. I can > attach Eclipse debugger to socket 5005 as remote Java app and step thru the > code with no issues. I make changes to a particular source file which maps > to bundle 340. > > I uninstall bundle 340, re-install from system file location (install -s > file:/foo/bar/baz). > > resolve 340 > refresh 340 > restart 340 > > bundle 340 is active. > > I terminate and re-launch debugger in Eclipse. I hit a breakpoint and step > thru the code and the lines of execution are no longer logical (skipping > over lines of code as if the code in runtime JVM and what is in the source > for Eclipse debugger don't match). > > I restart karaf. all bundles are active. I relaunch Eclipse debugger. > Now > I hit all logical breakpoints and can step thru the lines of code as > expected. > > Is this the expected experience (i.e. must I restart Karaf for the changes > to take affect for a single bundle update)? thx. > > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Debugging-Karaf-deployed-app-with-Eclipse-tp4043203.html > Sent from the Karaf - User mailing list archive at Nabble.com. >
