You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2016/12/04 21:18:59 UTC

[jira] [Comment Edited] (LOG4J2-1664) Improve OSGi unit tests

    [ https://issues.apache.org/jira/browse/LOG4J2-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15720618#comment-15720618 ] 

Gary Gregory edited comment on LOG4J2-1664 at 12/4/16 9:18 PM:
---------------------------------------------------------------

Patch applied, thank you!

Please verify and close unless there is more to do here. If so, please comment on what you see as the more to do.

Verifying that we have not built junk is an obvious one ;-)

Gary


was (Author: garydgregory):
Patch applied, thank you!

Please verify and close unless there is more to do here. If so, please comment on what you see as the more to do.

Verifying that we have not build junk is an obvious one ;-)

Gary

> Improve OSGi unit tests
> -----------------------
>
>                 Key: LOG4J2-1664
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1664
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API, Core
>    Affects Versions: 2.7
>            Reporter: Ludovic HOCHET
>             Fix For: 2.8
>
>         Attachments: patch-log4j2-1664-2.diff
>
>
> Following up on LOG4J2-1637, this ticket is to improve the OSGi unit tests. Ideally they should catch issues like LOG4J2-1637, but other improvements are welcome too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org