Why are we using the service-plugin model when we are dropping the platform
designations? Thought that we were going to drop all central platform
awareness from Pirk in favor of the ResponderLauncher. The service-plugin
model retains it in a roundabout way as we have to statically maintain the
list of known responders in
org.apache.pirk.responder.wideskies.spi.ResponderPlugin.

On Thu, Sep 22, 2016 at 5:36 AM, ellisonanne <g...@git.apache.org> wrote:

> Github user ellisonanne commented on a diff in the pull request:
>
>     https://github.com/apache/incubator-pirk/pull/93#discussion_r80005357
>
>     --- Diff: src/main/resources/META-INF/services/org.apache.pirk.
> responder.wideskies.spi.ResponderPlugin ---
>     @@ -0,0 +1,5 @@
>     +org.apache.pirk.responder.wideskies.mapreduce.MapReduceResponder
>     --- End diff --
>
>     Why are we using the service-plugin model when we are dropping the
> platform designations?
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

Reply via email to