RE: [POLL] Source code formatting conventions

I would not want to impose 1 vs the other. Could we articulate the important formatting elements (brace style, spaces vs tabs etc etc) in a document, and leave it to each developer to choose? We could then have a reference Jalopy xml file for anyone to use, but allow developers to choose how the do

DO NOT REPLY [Bug 31056] - (PATCH) Console appender doesn't notice changes to System.out/System.err

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 31056] - (PATCH) Console appender doesn't notice changes to System.out/System.err

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 31056] New: - (PATCH) Console appender doesn't notice changes to System.out/System.err

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

RE: cvs commit: logging-log4j/src/xdocs faq.xml

At 05:37 PM 9/3/2004, you wrote: Is it official policy to remove author tags from source files? Board minutes here discuss the issue: http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_02_18.txt D. Discussion: copyright ownership Although initiated due to the curren

RE: cvs commit: logging-log4j/src/xdocs faq.xml

Quoting "Shapira, Yoav" <[EMAIL PROTECTED]>: > > - Using tags like > > "@author http://logging.apache.org > ">The Logging Services Team" > > is encouraged. I'm not sure I see why this is encouraged? It is redundant. If Log4j is part of logging-services, the fact

RE: cvs commit: logging-log4j/src/xdocs faq.xml

Hi, To summarize from similar discussions on the commons and tomcat lists:   - Removing author tags without the author's consent: absolutely not, never.   - Removing author tags with the author's explicit consent in a publicly archived forum (e.g. any apache mailing list archive, but n

RE: cvs commit: logging-log4j/src/xdocs faq.xml

Is it official policy to remove author tags from source files? Board minutes here discuss the issue: http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_02_18.txt D. Discussion: copyright ownership Although initiated due to the current efforts for Spam Assassin,

RE: [POLL] Source code formatting conventions

At 03:39 PM 9/3/2004, Ceki Gülcü wrote: My interest on the formatting problem can be traced back a single issue. When a commit occurs, I'd like to be able to hone in on the changes by looking at the CVS notification message. When a developer makes logical changes to a file and at the same time chan

RE: [POLL] Source code formatting conventions

Hi, It's always interesting to see how two people can approach the same feature with such different goals ;) I agree with the coding convention and the FAQ's guidelines on contributing code, no issues there. I see code formatting as more than the indentation issue, though. I think there's va

RE: [POLL] Source code formatting conventions

At 02:52 PM 9/3/2004, Shapira, Yoav wrote: Hi, You're right that development has stopped on the open-source version of Jalopy, and that's a negative. However, Jalopy still works well and IIRC still supports a superset of the Eclipse formatting features. Do we really care whether Japoly is more p

cvs commit: logging-log4j/src/xdocs faq.xml

ceki2004/09/03 06:14:19 Modified:src/xdocs faq.xml Log: -Added a question about contributing to the FAQ. -Minor changes or enhancemetns to other questions Revision ChangesPath 1.2 +55 -14logging-log4j/src/xdocs/faq.xml Index: faq.xml ===

RE: [POLL] Source code formatting conventions

Hi, You're right that development has stopped on the open-source version of Jalopy, and that's a negative. However, Jalopy still works well and IIRC still supports a superset of the Eclipse formatting features. We don't want to require log4j developers to use a specific IDE, even if it's a fre

[POLL] Source code formatting conventions

Hello all, We used to rely on jalopy as the indentation tool for log4j. For quite a long time, the japoly plugin for eclipse did not run with version 3.0 of eclipse. This was a show stopper for many developers, including myself. It appears that the japoly plugin now supports eclipse 3.0. However, E

cvs commit: logging-log4j/docs .cvsignore

ceki2004/09/03 04:30:06 Modified:docs .cvsignore Log: The faq.html file (note the lower case) is generated automatically from 'src/xdocs/faq.xml' Revision ChangesPath 1.8 +1 -0 logging-log4j/docs/.cvsignore Index: .cvsignore

cvs commit: logging-log4j/docs FAQ.html

ceki2004/09/03 04:28:19 Removed: docs FAQ.html Log: Removing the FAQ.html file. It is now maintained as an xml file under /src/xdocs/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-ma

RE: log4j on JDK 1.5 (on Gump)

> Although log4j 1.2.x will not compile with JDK 1.5, it will run with > JDK 1.5 just fine. It does not make sense to make a new release for > log4j 1.2.x. Ahh... I agree then, it makes no sense. Cheers, Paul Smith - To unsubsc

RE: log4j on JDK 1.5 (on Gump)

At 11:41 PM 9/1/2004, you wrote: > >Which brings the question of, do we need to do this enum keyword > >replacement (not a big deal) in the log4j 1.2 branch and possibly have a > >log4j 1.2.9 release that's compatible with JDK 1.5 / 5.0? > > No, I don't think it's worth the effort. While I agree th