PTService should not be a SciJavaService

hinerm · hinerm · commit 93330a91c22e · 2013-12-20T14:57:07.000-06:00
PTService has a significant number of sub-interfaces and subclasses, all
of which are directly extended by various services through the
SciJava software stack (e.g. in ImageJ2). Having PTService as a
SciJavaService thus causes all of these implementing classes to get
pulled into Contexts created with "SciJavaService.class" - which is
supposed to just provide the core services.

Subclasses should instead implement the correct scoping interface (e.g.
SCIFIOService or ImageJService).
diff --git a/src/main/java/org/scijava/plugin/PTService.java b/src/main/java/org/scijava/plugin/PTService.java
@@ -37,7 +37,7 @@
 
 import java.util.List;
 
-import org.scijava.service.SciJavaService;
+import org.scijava.service.Service;
 
 /**
  * A service for managing a particular sort of {@link SciJavaPlugin}.
@@ -84,7 +84,7 @@
  * @see TypedService
  * @see WrapperService
  */
-public interface PTService<PT extends SciJavaPlugin> extends SciJavaService {
+public interface PTService<PT extends SciJavaPlugin> extends Service {
 
 	/**
 	 * Gets the service responsible for discovering and managing this service's
