From d72a587ab2ff900c81ebd57f7990f8d379fbe474 Mon Sep 17 00:00:00 2001
From: Stephan Schroevers <stephan.schroevers@teampicnic.com>
Date: Sun, 25 Sep 2022 11:00:08 +0200
Subject: [PATCH] Flag classpath issue

---
 refaster-runner/pom.xml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/refaster-runner/pom.xml b/refaster-runner/pom.xml
index c6a591cb..253b8423 100644
--- a/refaster-runner/pom.xml
+++ b/refaster-runner/pom.xml
@@ -41,6 +41,14 @@
         <dependency>
             <groupId>${project.groupId}</groupId>
             <artifactId>refaster-compiler</artifactId>
+            <!-- XXX: This `runtime` scope declaration ensures that
+            `AnnotatedCompositeCodeTransformer` instances can be deserialized.
+            It also makes our custom Refaster annotations available. The issue
+            with this setup is that `refaster-compiler` has *non*-`provided`
+            dependency declarations on Error Prone, as it should be able to
+            function independently. This could cause classpath issues for users
+            of *this* module. Consider moving
+            `AnnotatedCompositeCodeTransformer` back to `refaster-support`. -->
             <scope>runtime</scope>
         </dependency>
         <dependency>