[jira] [Issue Comment Deleted] (LOG4J2-1563) Log4j 2.6.2 can lose exceptions when a security manager is present

["Jason Tedor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Tedor updated LOG4J2-1563:
--------------------------------
    Comment: was deleted

(was: Please do not attribute this to the tooling, this has nothing to do with the tooling. The right tooling is available on the major platforms.

For me personally I was not happy to learn that this is the practice after my contribution was accepted, this is the only open source project I've seen conducted this way (there might be others, but this is the first I've seen).

If people spend time carefully preparing a patch and crafting a commit message, the entirety of their work (which is more than just the code) should be integrated.
)

> Log4j 2.6.2 can lose exceptions when a security manager is present
> ------------------------------------------------------------------
>
>                 Key: LOG4J2-1563
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1563
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.6.2
>            Reporter: Jason Tedor
>            Assignee: Gary Gregory
>             Fix For: 2.7
>
>         Attachments: 0001-Unify-handling-of-throwables-when-loading-class.patch, 0002-Remove-policy-in-throwable-proxy-security-test.patch, throwable-proxy-security-exception-2.6.2.patch
>
>
> When Log4j is rendering an exception, it can attempt to load classes that it does not have permissions to load when a security manager is present.
> I have a patch and a failing test case for this; I will submit it shortly.
> This is the backport for LOG4J2-1560.



--
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