"Aaron Smuts" <[EMAIL PROTECTED]> wrote: > Deprecation causes gump build failures?
When somebody 'deprecates' a method in the code you depend upon, not using warning, but removing the method, or changes the signature, ... then yes. The purpose of Gump is to detect these issues before their libraries get released into the field, and your code run atop it & crashes. Gump is trying to reduce Jar Hell. regards Adam > > cannot resolve symbol [javac] symbol : method callRemoteMethods > > > (<nulltype>,java.lang.String,java.lang.String,java.io.Serializable,int,int) > > [javac] location: class > > org.jgroups.blocks.RpcDispatcher > > [javac] RspList rsp_list = > > disp.callRemoteMethods( null, > > "handleGet", led.ce.getCacheName(), led.ce.getKey(), > > [javac] ^ > > [javac] Note: Some input files use or override a > > deprecated API. > > [javac] Note: Recompile with -deprecation for > > details. > > [javac] 1 error > > See: > > > > > http://brutus.apache.org/gump/public/jakarta-turbine-jcs/jakarta-turbine-jcs/index.html Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
