It is a real case in our inner project "http-server" which is build using netty. Usually we add one or more class to add a new future.Then update the version, Gray released.
Recently, I resolve the netty conflict using maven shade plugin and update the version.All version not equal to the target version will using different instrumentation. I think this logic is very difficult to express by the witness class. On the other hand, If people have to use the Uranus project to find a witness, It's a little more expensive to resolve the problem. Think about this: If I have a runtime method invoke error,Why should I use a witness class to resolve it? 在 2020/12/28 下午8:18，“Sheng Wu”<[email protected]> 写入: Hi I am not sure whether this is a real case. Is there really existing case 2 versions including 100% the same codes? There is a project created by the community called, uranus, which you could find on the website. https://skywalking.apache.org/docs/ This is a tool to help on locating witness class. Sheng Wu 吴晟 Twitter, wusheng1108 Li BingLong(智能平台) <[email protected]> 于2020年12月28日周一 下午7:33写道： > Sometimes its too difficult to find a witness class. > Maybe the version 2 has all class in version 1.How can I define a > instrumentation if I want the version 1 to be instrument? > In my opinion,we usually want to instrument a specified method. If we > dont have other ways,some code about a method may be a good “witness > code”other than witness class. >
