DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40342>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40342 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |33862 nThis| | Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Additional Comments From [EMAIL PROTECTED] 2006-08-30 12:34 ------- I didnt really look at what java1.5 did, only noticed that the dependency logic broke and that the rmic docs say "We no longer do -compat" by default -so we switched rmic back to retaining the defaults. the trouble with trying to be clever about knowing which jvm has what defaults is that we often end up getting it wrong, as they change behaviours on new JDKs (like here). Supporting third party JDKs and as yet unreleased JDKs are extra trouble. Going to reopen as we could look for skeletons, maybe. however, my other point about default stubs still stands. Imagine you write an app on java1.4 & redistribute the app with source. the moment someone builds on java1.5, they end up producing something that is incompatible. now, what they do with their .class files is normally their problem, but RMI is a network protocol. By abandoning compatibility you are producing code that doesnt interop over the network, and that is a bad thing. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
