logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1428) Scala friedly overloading in MessageFactory(2)
Date Mon, 13 Jun 2016 22:52:03 GMT

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

Remko Popma commented on LOG4J2-1428:

Ouch! The problem is that we have already published this API. Renaming methods would break
binary compatibility. 

What is the consequence of the issue in our case? The MessageFactory.newMessage(String) method
always gets selected by Scala? That doesn't seem like a big problem, or do I misunderstand?

> Scala friedly overloading in MessageFactory(2)
> ----------------------------------------------
>                 Key: LOG4J2-1428
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1428
>             Project: Log4j 2
>          Issue Type: Wish
>          Components: API
>    Affects Versions: 2.6, 2.6.1
>            Reporter: Mikael Ståldal
> Due to a known issue (https://issues.scala-lang.org/browse/SI-4775), Scala cannot resolve
all the {{newMessage}} methods in {{MessageFactory(2)}} properly.

This message was sent by Atlassian JIRA

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

View raw message