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=20699>. 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=20699 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|rmic and seaprate |[PATCH] rmic and seaprate |input/output directories |input/output directories ------- Additional Comments From [EMAIL PROTECTED] 2005-08-17 22:31 ------- That is also my ugly workaround for the moment. I don't like it, because rmic already provides the option to do this for us. (And as stated in comment #4, the current implementation even prevents us from using it.) Granted, this hopefully will never be a concern, but what if someone wrote a class called *_Stub.class that wasn't even a stub or generated by rmic? Unlikely, but always plan for the worst-case scenarios... To me, this seems like rather important functionality that's missing from RMIC, b/c the stubs are generated from the server for use on the client. Good code organization should probably have the interfaces, server, and client in 3 separate source trees. Alexey, is there any chance at getting this committed into at least HEAD, sooner than later? Id really like to include this functionality into my build scripts, but it will cause problems for others using the code base. Id rather have them use something directly from Ant, rather than everyone having to manually patch. Thanks!! -- 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]
