name: TensorFlow Lite in Play Services issue
about: Use this template for issues with TensorFlow Lite in Google Play Services
labels: 'comp:lite-in-play-services'

---

**System information**
- Android Device information (use `adb shell getprop ro.build.fingerprint`
  if possible):
- TensorFlow Lite in Play Services SDK version (found in `build.gradle`):
- Google Play Services version
  (`Settings` > `Apps` > `Google Play Services` > `App details`):

import org.apache.maven.api.annotations.ThreadSafe;

/**
 * Marker interface for all services provided by the {@link Session}.
 * <p>
 * Services can be retrieved from the session using the
 * {@link Session#getService(Class)} method.
 *
 * @since 4.0.0
 * @see Session#getService(Class)
 */
@Experimental
@ThreadSafe

  public ServiceManager startAsync() {
    for (Service service : services) {
      checkState(service.state() == NEW, "Not all services are NEW, cannot start %s", this);
    }
    for (Service service : services) {
      try {
        state.tryStartTiming(service);
        service.startAsync();
      } catch (IllegalStateException e) {
        // This can happen if the service has already been started or stopped (e.g. by another

  public ServiceManager startAsync() {
    for (Service service : services) {
      checkState(service.state() == NEW, "Not all services are NEW, cannot start %s", this);
    }
    for (Service service : services) {
      try {
        state.tryStartTiming(service);
        service.startAsync();
      } catch (IllegalStateException e) {
        // This can happen if the service has already been started or stopped (e.g. by another

        }
      },
      {
        "subprojects": [
          "base-services",
          "flow-services",
          "input-tracking",
          "internal-integ-testing",
          "jvm-services",
          "messaging",
          "persistent-cache",
          "plugins-java",
          "problems",
          "process-memory-services",
          "testing-base-infrastructure"
        ],

  }

  private static void assertState(
      ServiceManager manager, Service.State state, Service... services) {
    Collection<Service> managerServices = manager.servicesByState().get(state);
    for (Service service : services) {
      assertEquals(service.toString(), state, service.state());

     *
     * @throws org.apache.maven.api.services.MavenException if not called from the within a mojo execution
     */
    @Nonnull
    Map<String, Object> getPluginContext(@Nonnull Project project);

    /**
     * Retrieves the service for the interface
     *
     * @throws NoSuchElementException if the service could not be found
     */
    @Nonnull
    <T extends Service> T getService(@Nonnull Class<T> clazz);

    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "base-services",
    "path": "platforms/core-runtime/base-services",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "base-services-groovy",
    "path": "platforms/core-configuration/base-services-groovy",
    "unitTests": true,
    "functionalTests": false,
    "crossVersionTests": false

Introduce a "UI" architecture module to the core platform, and move the user interaction services to this new module.

This includes:

- Logging and progress services.
- Problem generation services (aka the "problems API").
- User prompting services.
- Build options infrastructure.
- The console and CLI, as a specific implementation of these services.

 * It simply delegates to Maven4 API {@link org.apache.maven.api.services.Prompter}.
 */
@Experimental
@Named
@Singleton
@Priority(10)
public class LegacyPlexusInteractivity implements Prompter, InputHandler, OutputHandler {
    private final org.apache.maven.api.services.Prompter prompter;

    @Inject
    public LegacyPlexusInteractivity(org.apache.maven.api.services.Prompter prompter) {
        this.prompter = prompter;
    }