[Java] [Android] Jersey2 library request/issue - suppress warning log in android

Description

When I generate swagger client for java using Jersey 2 library and use it with both java and android project (which works in android), there are warning thrown by client because of use of java.awt.* class in jersey unsupported by Android. Although these are just warnings but there are way to suppress such warnings. (and maybe make jersey2 client library available for android platform?)

The main purpose of using jersey client in Android is to support circular dependency json sent by server (Jsog Jackson)

Swagger-codegen version

2.3.1, older one (with no version command)

Suggest a fix/enhancement

The way to suppress those warnings in logs is to add a feature to client that let hk2 not search for non available files.

Sample code for feature (that i am using with generated code)

import javax.ws.rs.core.Feature;
import javax.ws.rs.core.FeatureContext;
import org.glassfish.hk2.api.Descriptor;
import org.glassfish.hk2.api.Filter;
import org.glassfish.hk2.utilities.binding.AbstractBinder;

/**
 *
 * @author akshit
 */
public class AndroidFriendlyFeature implements Feature {
    @Override
    public boolean configure(FeatureContext context) {
      context.register(new AbstractBinder() {
          @Override
          protected void configure() {
              addUnbindFilter(new Filter() {
                  @Override
                  public boolean matches(Descriptor d) {
                      String implClass = d.getImplementation();
                      return implClass.startsWith("org.glassfish.jersey.message.internal.DataSource")
                       || implClass.startsWith("org.glassfish.jersey.message.internal.RenderedImage");
                  }
              });
          }
      });
      return true;
    }
}

then add it to client on ApiClient.java buildHttpClient Method

clientConfig.register(AndroidFriendlyFeature.class);

Start with the generated ApiClient.java buildHttpClient method and the Jersey 2 client configuration. Review the proposed AndroidFriendlyFeature and its HK2 filters, then check the Java client templates that produce this code. Done means the generated Android client suppresses the unsupported java.awt-related warnings without disrupting regular Java clients.