On 11/27/06, Martin Cooper <[EMAIL PROTECTED]> wrote:
Of course it is. These changes are incompatible in that some people's code will no longer compile against the new version.
In this particular case, the situation is like this: If people are actually depending on the presence of this code, then they have, for example, that this exception is thrown. An assumption, on which they possibly depend, and which is no longer true. My personal style of coding is that I would always prefer to be notified of such issues in a very clear manner rather than having someone who ensures that I believe everything is alright. Besides, let me quote yourself: Multipartstream isn't (supposed to be) part of the public API Sigh, I'll reintroduce this nonsense.
I'm sorry, but I find your attitude quite disturbing here. You come in on a project that has been very close to Checkstyle-clean for years, you make changes that introduce hundreds of new violations, and you have the gall to say that you refuse to fix the ones you don't agree with? That's not how we work here at Commons either.
Yes, I share the feeling that this is not the style of work at Commons. It rather seems to be having someone to pick up an almost dead project, revitalize it with radical internal changes at the cost of almost no public API change, give him no freedback without request and even then almost no response to questions, suggestions and votes (you being the almost sole exception), but whenever it comes to a release, force him to do the important stuff like removing trailing blanks, convert tabs into blanks, comment methods like SomeInputStream.(close|read), and stuff like that. Sorry, but I do indeed have gall in the sense of coming up from my waist. Jochen -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
