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

Posted to notifications@logging.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/03/28 21:16:00 UTC

[jira] [Commented] (LOG4J2-1882) Migrate log4j-api-scala to SBT

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

ASF subversion and git services commented on LOG4J2-1882:
---------------------------------------------------------

Commit dcb1e2d6b6f9470c69ebed4ee8c60de6c782e2c7 in logging-log4j-scala's branch refs/heads/sbt from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j-scala.git;h=dcb1e2d ]

LOG4J2-1882 - Merge API modules into one using SBT


> Migrate log4j-api-scala to SBT
> ------------------------------
>
>                 Key: LOG4J2-1882
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1882
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Scala API
>            Reporter: Matt Sicker
>            Assignee: Matt Sicker
>            Priority: Major
>
> One handy feature that would reduce quite an amount of duplication would be the [cross build feature|http://www.scala-sbt.org/0.13/docs/Cross-Build.html]. Since the Scala API is in its own repo, using SBT for it makes more sense than sticking with Maven.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)