From 9fc68e19309cef139c4827fbed76952011995e10 Mon Sep 17 00:00:00 2001
From: Adriaan Moors <adriaan.moors@typesafe.com>
Date: Tue, 24 Jun 2014 15:54:10 +0200
Subject: Remove deprecationWarning, currentReporting from Reporting

This moves us a bit closer to the goal of having a single
entry point to reporting.

Must modularize Reporting a bit so it can be used in Variances
(need a reference to `currentRun` in `reflect.internal.Reporting`).
---
 bincompat-forward.whitelist.conf | 12 ++++++++++++
 1 file changed, 12 insertions(+)

(limited to 'bincompat-forward.whitelist.conf')

diff --git a/bincompat-forward.whitelist.conf b/bincompat-forward.whitelist.conf
index dbf0807999..30dac79974 100644
--- a/bincompat-forward.whitelist.conf
+++ b/bincompat-forward.whitelist.conf
@@ -242,6 +242,18 @@ filter {
     {
         matchName="scala.reflect.runtime.JavaUniverse.reporter"
         problemName=MissingMethodProblem
+    },
+    {
+       matchName="scala.reflect.runtime.JavaUniverse$PerRunReporting"
+       problemName=MissingClassProblem
+    },
+    {
+       matchName="scala.reflect.runtime.JavaUniverse.currentRun"
+       problemName=MissingMethodProblem
+    },
+    {
+       matchName="scala.reflect.runtime.JavaUniverse.PerRunReporting"
+       problemName=MissingMethodProblem
     }
   ]
 }
-- 
cgit v1.2.3