[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14984861#comment-14984861 ]
Gary Gregory commented on LOG4J2-1181: -------------------------------------- Mikael, Thank you for getting this started. I was able to run the tests OK for the 2.11 projects in Eclipse set up with m2e. For the 2.10 project I get: {noformat} Description Resource Path Location Type More than one scala library found in the build path (C:/eclipse/4.5/plugins/org.scala-lang.scala-library_2.11.7.v20150622-112736-1fbce4612c.jar, C:/Users/ggregory/.m2/repository/org/scala-lang/scala-library/2.10.6/scala-library-2.10.6.jar).At least one has an incompatible version. Please update the project build path so it contains only one compatible scala library. log4j-scala_2.10 Unknown Scala Classpath Problem scalatest_2.10-2.2.5.jar of log4j-scala_2.10 build path is cross-compiled with an incompatible version of Scala (2.10.0). In case this report is mistaken, this check can be disabled in the compiler preference page. log4j-scala_2.10 Unknown Scala Version Problem {noformat} How can we get this to work in Eclipse? Both projects test fine from the Maven command line, so that's good. I'm not sure I understand the goal here though. I only see a {{LoggerTest}} class. Don't we want to provide wrappers for at least {{LogManager}}, {{Logger}}, {{MarkerManager}}, basically all of the "main" {{log4j-api}} classes. I'm starting to think that the modules should be called {{log4j-api-scala_2.10}} and {{log4j-api-scala_2.11}} to reflect that we are dealing with the Scala version of {{log4j-api}}. I'm not a Scala guru yet, so I'll appreciate any insights here ;-) > Scala wrapper for Log4j 2 API > ----------------------------- > > Key: LOG4J2-1181 > URL: https://issues.apache.org/jira/browse/LOG4J2-1181 > Project: Log4j 2 > Issue Type: New Feature > Components: API > Affects Versions: 2.4.1 > Reporter: Mikael Ståldal > > Scala wrapper for Log4j 2 API which makes use of Scala features like macros > and string interpolation. > Inspired from [Typesafe's Scala > Logging|https://github.com/typesafehub/scala-logging] but should use Log4j 2 > directly and expose its features. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org