*
 * @since 4.0.0
 */
@Experimental
public interface EncryptInvokerRequest extends InvokerRequest<EncryptOptions> {
    // This interface doesn't declare any additional methods beyond those inherited from InvokerRequest.
    // It serves to type-specify the Options as EncryptOptions for encryption-related requests.

 *
 * <p>
 * Reports simple superclass changes (e.g. the removal of a superclass) as a breaking change, as it affects what methods can be
 * called with the given type, even if the methods and fields inherited don't change.
 * </p>
 */
class BinaryBreakingSuperclassChangeRule extends AbstractSuperClassChangesRule {

    BinaryBreakingSuperclassChangeRule(Map<String, Object> params) {
        super(params)
    }

  <modules>
    <module>../inheritance</module><!-- current directory == inheritance -->
  </modules>

  <!-- 5 urls in the pom will be inherited with path added -->
  <url>http://www.apache.org/path/to/parent/</url>
  <scm>
    <connection>scm:my-scm:http://domain.org/base</connection>
    <developerConnection>scm:my-scm:https://domain.org/base/</developerConnection>

// {
//   "version": "1",
//   "format": "XXXXX",
//   "XXXXX": {
//
//   }
// }
// Here "XXXXX" depends on the backend, currently we have "fs" and "xl" implementations.
// formatMetaV1 should be inherited by backend format structs. Please look at format-fs.go
// and format-xl.go for details.

// Ideally we will never have a situation where we will have to change the
// fields of this struct and deal with related migration.

  public static InternerBuilder newBuilder() {
    return new InternerBuilder();
  }

  /**
   * Returns a new thread-safe interner which retains a strong reference to each instance it has
   * interned, thus preventing these instances from being garbage-collected. If this retention is
   * acceptable, this implementation may perform better than {@link #newWeakInterner}.
   */
  public static <E> Interner<E> newStrongInterner() {

  <version>11-SNAPSHOT</version>
  <name>Model urls inheritance test child</name>
  <description>Flat directory structure case: module = ../child directory path + child directory path != child-artifact-id</description>

  <!-- 5 inherited urls with ../${project.artifactId} added to parent -->
  <url>http://www.apache.org/path/to/parent/../child-artifact-id/</url>
  <scm>
    <connection>scm:my-scm:http://domain.org/base/../child-artifact-id</connection>

</pre>

<p>
When using a generic function, type arguments may be provided explicitly,
or they may be partially or completely <a href="#Type_inference">inferred</a>
from the context in which the function is used.
Provided that they can be inferred, type argument lists may be omitted entirely if the function is:
</p>

<ul>
<li>
	<a href="#Calls">called</a> with ordinary arguments,
</li>
<li>

		podCount := podCountByRevision(allPods[resource.Namespace(namespace.Name)], revision)
		if len(podCount) == 0 {
			// This namespace has no pods, but we wish to display it if new pods will be auto-injected
			if revision != "" {
				podCount[revision] = revisionCount{}
			}
		}
		for injectedRevision, count := range podCount {
			if outputCount == 0 {

  <version>11-SNAPSHOT</version>

  <name>Model inheritance test parent: module path != artifactId</name>

  <modules>
    <module>child</module>
  </modules>

  <!-- 5 URLs in the pom will be inherited with path added -->
  <url>http://www.apache.org/</url>
  <scm>
    <connection>scm:my-scm:http://domain.org/base</connection>
    <developerConnection>scm:my-scm:https://domain.org/base/</developerConnection>

  <version>11-SNAPSHOT</version>
  <name>Model urls inheritance test child</name>
  <description>Flat directory structure case: module = ../child-artifact-id + child directory path != child-artifact-id</description>

  <!-- 5 inherited urls with ../${project.artifactId} added to parent -->
  <url>http://www.apache.org/path/to/parent/../child-artifact-id/</url>
  <scm>
    <connection>scm:my-scm:http://domain.org/base/../child-artifact-id</connection>