From eeada0a65ac592c258ea98bf7762964e42ebb533 Mon Sep 17 00:00:00 2001
From: kohsuke <kohsuke@71c3de6d-444a-0410-be80-ed276b4c234a>
Date: Thu, 8 Feb 2007 17:32:05 +0000
Subject: [PATCH] turns out my fix was wrong. DefaultClassRealm in classworlds
 is child-first delegation, so when loading classes in a child container
 (which creates its own realm), MojoScanner interface ends up loaded locally.
 So really the only solution is to hide the maven-plugin-tools-api.jar from
 embedded Maven.

git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@2106 71c3de6d-444a-0410-be80-ed276b4c234a
---
 war/pom.xml | 14 --------------
 1 file changed, 14 deletions(-)

diff --git a/war/pom.xml b/war/pom.xml
index 32cb480433..31afda11e5 100644
--- a/war/pom.xml
+++ b/war/pom.xml
@@ -206,19 +206,5 @@
         </exclusion>
       </exclusions>
     </dependency>
-    <!--
-      When Hudson runs in Jetty launched from Maven, plugin-tools-api.jar visible
-      to Jetty mojo becomes visible to Hudson running inside it.
-
-      This causes a problem because whereas embedded Maven should have loaded another copy
-      of this in its own classworlds, instead we'd end up seeing this class from Jetty.
-      So to prevent this problem, make sure to load this jar from the web application itself,
-      so that it can still resolve the same underlying Maven classes.
-    -->
-    <dependency>
-      <groupId>org.apache.maven</groupId>
-      <artifactId>maven-plugin-tools-api</artifactId>
-      <version>2.0.4</version>
-    </dependency>
   </dependencies>
 </project>
\ No newline at end of file
-- 
GitLab