<resourceBundle>org.apache:apache-jar-resource-bundle:1.0</resourceBundle>
                  </resourceBundles>
                </configuration>
              </execution>
            </executions>
          </plugin>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-source-plugin</artifactId>
            <version>2.0.2</version>

                <!-- JDK 9 minimal source and target versions are 1.6 -->
                <jdkVersion>1.6</jdkVersion>
            </properties>
            <build>
                <plugins>
                    <plugin>
                        <artifactId>maven-javadoc-plugin</artifactId>
                        <configuration>
                            <source>1.6</source>
                        </configuration>

  feedback for that case. However, when offline mode is declared, nothing
  earmarked as remote should be accessed, regardless of whether it is actually
  a physically local resource.

  NOTE: One side-effect of this design change is that all offline-mode code can
  be isolated to maven-core, maven-plugin-descriptor, and [possibly]
  maven-artifact. Usage of maven-wagon will be determined by an offline-aware

application or extension of the application in the form of plugins.

In the short term we are working with the model where the URI maps to a resource, and the resource itself is a Plexus component which can itself have a reference to the host application in order to perform its work. This may not occur in the first versions of the plugin API but a resource needs to simply become the mapping mechanism by which parameters are taken from the REST side of the application and mapped into a method call...