May 2008 - logback-dev - mailman3.qos.ch

[JIRA] Created: (LBCLASSIC-52) Allow multiple addresses for "to" property of SMTPAppender
by JIRA Administrator (JIRA) 11 Jul '12

11 Jul '12

Allow multiple addresses for "to" property of SMTPAppender ---------------------------------------------------------- Key: LBCLASSIC-52 URL: http://jira.qos.ch/browse/LBCLASSIC-52 Project: logback-classic Issue Type: Improvement Reporter: Andrey Utkin Assignee: Ceki Gulcu SMTPAppender don`t allow to specify multiple addresses in single "to" property. So that, it is (almost?) impossible to specify multiple "to" addresses via variable substitution. We should know exact number of addresses (variables) to specify appropriate quantity of <to> elements. But number of "to" addresses could be changed during application using and differ from customer to customer. So, IMFO it will be helpful to allow specifying multiple addresses in one <to> element. Multiple addresses could be separated by comma, for example (as comma is not valid character for email address). Right now we are using simple workaround. We subclass SMTPAppender and overwrite addTo(): {code} @Override public void addTo(String to) { StringTokenizer st = new StringTokenizer(to, ","); while(st.hasMoreTokens()) { super.addTo(st.nextToken().trim()); } } {code} This solution works just fine for us. May be it will be good to include this feature in core logback too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 6

[JIRA] Created: (LBGENERAL-18) Attachments are lost during migration from bugzilla to JIRA
by JIRA Administrator (JIRA) 19 Aug '08

19 Aug '08

Attachments are lost during migration from bugzilla to JIRA ----------------------------------------------------------- Key: LBGENERAL-18 URL: http://jira.qos.ch/browse/LBGENERAL-18 Project: logback-general Issue Type: Bug Reporter: Roland Klein Assignee: Ceki Gulcu Attachments are lost during migration from bugzilla to JIRA The Attachments are lost during migration from bugzilla to JIRA. e.g. bugzilla #107 -> JIRA #32 Patch is gone -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

2 2

svn commit: r1701 - logback/trunk/logback-classic/src/main/java/org/slf4j/impl
by noreply.ceki＠qos.ch 27 May '08

27 May '08

Author: ceki Date: Tue May 27 22:01:26 2008 New Revision: 1701 Modified: logback/trunk/logback-classic/src/main/java/org/slf4j/impl/LogbackMDCAdapter.java Log: - getCopyOfPropertyMap was renamed as getCopyOfContextMap in SLF4J 1.5.1 Modified: logback/trunk/logback-classic/src/main/java/org/slf4j/impl/LogbackMDCAdapter.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/org/slf4j/impl/LogbackMDCAdapter.java (original) +++ logback/trunk/logback-classic/src/main/java/org/slf4j/impl/LogbackMDCAdapter.java Tue May 27 22:01:26 2008 @@ -124,7 +124,7 @@ * Return a copy of the current thread's context map. * Returned value may be null. */ - public Map getCopyOfPropertyMap() { + public Map getCopyOfContextMap() { HashMap<String, String> hashMap = inheritableThreadLocal.get(); if (hashMap == null) { return null;

1 0

svn commit: r1700 - logback/trunk/logback-classic/src/main/java/org/slf4j/impl
by noreply.ceki＠qos.ch 27 May '08

27 May '08

Author: ceki Date: Tue May 27 20:36:24 2008 New Revision: 1700 Modified: logback/trunk/logback-classic/src/main/java/org/slf4j/impl/LogbackMDCAdapter.java Log: - catching up with SLF4J 1.5.1 by adding the getCopyOfPropertyMap Modified: logback/trunk/logback-classic/src/main/java/org/slf4j/impl/LogbackMDCAdapter.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/org/slf4j/impl/LogbackMDCAdapter.java (original) +++ logback/trunk/logback-classic/src/main/java/org/slf4j/impl/LogbackMDCAdapter.java Tue May 27 20:36:24 2008 @@ -121,6 +121,20 @@ } /** + * Return a copy of the current thread's context map. + * Returned value may be null. + */ + public Map getCopyOfPropertyMap() { + HashMap<String, String> hashMap = inheritableThreadLocal.get(); + if (hashMap == null) { + return null; + } else { + return new HashMap<String, String>(hashMap); + } + } + + + /** * Returns the keys in the MDC as a {@link Set}. The returned value can be * null. */

1 0

[JIRA] Commented: (GENERAL-18) Attachments are lost during migration from bugzilla to JIRA
by JIRA Administrator (JIRA) 22 May '08

22 May '08

[ http://jira.qos.ch/browse/GENERAL-18?page=com.atlassian.jira.plugin.system.… ] JIRA Administrator commented on GENERAL-18: ------------------------------------------- Apparently, it is a well-known problem with a not-so-convenient-but-ok fix: http://confluence.atlassian.com/display/JIRA/Migrating+from+Bugzilla+3.0.3 > Attachments are lost during migration from bugzilla to JIRA > ----------------------------------------------------------- > > Key: GENERAL-18 > URL: http://jira.qos.ch/browse/GENERAL-18 > Project: logback-general > Issue Type: Bug > Components: build-structure > Affects Versions: unspecified > Reporter: Roland Klein > Assignee: Logback dev list > > The Attachments are lost during migration from bugzilla to JIRA. > e.g. bugzilla #107 -> JIRA #32 Patch is gone -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[Bug 107] Specificy the config file to use as a System property
by bugzilla-daemon＠pixie.qos.ch 22 May '08

22 May '08

show_bug.cgi?id=107 Ceki Gulcu <noreply.ceki(a)qos.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |noreply.ceki(a)qos.ch --- Comment #7 from Ceki Gulcu <noreply.ceki(a)qos.ch> 2008-05-22 22:35:11 --- x -- Configure bugmail: userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[JIRA] Commented: (GENERAL-18) Attachments are lost during migration from bugzilla to JIRA
by Ceki Gulcu (JIRA) 22 May '08

22 May '08

[ http://jira.qos.ch/browse/GENERAL-18?page=com.atlassian.jira.plugin.system.… ] Ceki Gulcu commented on GENERAL-18: ----------------------------------- Hello Roland, That sounds pretty bad. I'll look into it. > Attachments are lost during migration from bugzilla to JIRA > ----------------------------------------------------------- > > Key: GENERAL-18 > URL: http://jira.qos.ch/browse/GENERAL-18 > Project: logback-general > Issue Type: Bug > Components: build-structure > Affects Versions: unspecified > Reporter: Roland Klein > Assignee: Logback dev list > > The Attachments are lost during migration from bugzilla to JIRA. > e.g. bugzilla #107 -> JIRA #32 Patch is gone -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

Migrated to JIRA
by Ceki Gulcu 20 May '08

20 May '08

The logback project now relies on to JIRA instead of Bugzilla as its bug tracking system. Previous bug reports as well existing users in Bugzilla have been migrated to JIRA. Thus, from now on, please use JIRA to create or edit bug reports. The url is: http://jira.qos.ch/ Let me know if you encounter any problems. -- Ceki Gülcü

1 0

svn commit: r1699 - logback/trunk/logback-site/src/site/pages
by noreply.ceki＠qos.ch 20 May '08

20 May '08

Author: ceki Date: Tue May 20 17:31:47 2008 New Revision: 1699 Modified: logback/trunk/logback-site/src/site/pages/bugreport.html Log: - migrated from bugzilla to JIRA Modified: logback/trunk/logback-site/src/site/pages/bugreport.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/bugreport.html (original) +++ logback/trunk/logback-site/src/site/pages/bugreport.html Tue May 20 17:31:47 2008 @@ -24,58 +24,68 @@ <h2>Before you report a bug</h2> -<p> -The logback community consists of those who use logback and its modules, -help answer questions on discussions lists, contribute documentation and patches, -and those who develop and maintain the code for logback and its modules. -Almost all those who assist on a day to day basis resolving bug reports do this for -a wide variety of reasons, and almost all of them do this on their own time. -</p> -<p> -Many bugs reported end up not being a bug in logback, but are due to misconfiguration, -problems caused by installed applications, the operating system, etc. -</p> -<p> -Before reporting a bug please make every effort to resolve the problem yourself. -Just reporting a bug will not fix it. A good bug report includes a detailed description -of the problem and a succinct test case which can reproduce the problem. -</p> - -<h3>Review the documentation</h3> -<p> -Review the documentation for the version of component you are using. -The problem you are having may already be addressed in the docs. -</p> - -<h3>Search the mailing list archives</h3> -<p> -It is very likely you are not the first to run into a problem. -Others may have already found a solution. -Our various mailing lists are likely to have discussed this problem before. -</p> - -<h3>Search Bugzilla</h3> - -<p> -Please search the bug database to see if the bug you are seeing has already been reported. -The bug may have already been fixed and is available in a later version. -If someone else has reported the same bug, you could add supporting information to help reproduce and resolve the bug. -</p> -<ul> - <li><a href="http://bugzilla.qos.ch/query.cgi">Search for logback bugs</a></li> -</ul> - -<h2>Reporting with Bugzilla</h2> -<p> -Only after you have exhausted the aforementioned steps, should you file a formal report in bugzilla. -</p> -<p> -Please make sure you provide as much information as possible. -Its very hard to fix a bug if the person looking into the problem can't reproduce it. -</p> -<ul> - <li><a href="http://bugzilla.qos.ch/enter_bug.cgi">Report new logback bug</a></li> -</ul> + <p>The logback community consists of those who use logback and its + modules, help answer questions on discussions lists, contribute + documentation and patches, and those who develop and maintain its + code. Almost all those who assist on a day to day basis resolving + bug reports do this for a wide variety of reasons, and almost all of + them do this on their own time.</p> + + <p>Many bugs reported end up not being a bug in logback, but are due + to misconfiguration, problems caused by installed applications, the + operating system, etc. + </p> + + <p>Before reporting a bug please make every effort to resolve the + problem yourself. Just reporting a bug will not fix it. A good bug + report includes a detailed description of the problem and a succinct + test case which can reproduce the problem. + </p> + + <h3>Review the documentation</h3> + + <p>Review the documentation for the version of component you are + using. The problem you are having may already be addressed in the + docs. + </p> + + <h3>Search the mailing list archives</h3> + + <p>It is very likely you are not the first to run into a problem. + Others may have already found a solution. Our various mailing lists + are likely to have discussed this problem before. + </p> + + <h3>Search JIRA</h3> + + <p>Please search the bug database to see if the bug you are seeing + has already been reported. The bug may have already been fixed and + is available in a later version. If someone else has reported the + same bug, you could add supporting information to help reproduce and + resolve the bug. + </p> + + <ul> + <li><a href="http://jira.qos.ch/secure/IssueNavigator.jspa">Search + for logback bugs</a></li> + </ul> + + <h2>Reporting with bugs</h2> + + <p> Only after you have exhausted the aforementioned steps, should + you file a formal report in JIRA, our bug tracking system. + </p> + + <p>Please make sure you provide as much information as possible. + Its very hard to fix a bug if the person looking into the problem + can't reproduce it. + </p> + + <ul> + <li><a + href="http://jira.qos.ch/secure/CreateIssue!default.jspa">Report + new logback bug</a></li> + </ul> <script src="templates/footer.js"></script> </div>

1 0

[Bug 138] support looking up property files from classpath resources
by bugzilla-daemon＠pixie.qos.ch 19 May '08

19 May '08

show_bug.cgi?id=138 Eduardo Ito <ziba(a)summa-tech.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ziba(a)summa-tech.com --- Comment #1 from Eduardo Ito <ziba(a)summa-tech.com> 2008-05-19 22:10:20 --- That would be very useful. I was just trying to do this, when discovered that Logback can only read properties from the file system. Is it being considered for newer versions? -- Configure bugmail: userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0