# o dbfluteDiconPackageName: (NotRequired - Default '../resources')
# o dbfluteDiconFileName: (NotRequired - Default 'dbflute.dicon')
# o j2eeDiconResourceName: (NotRequired - Default 'j2ee.dicon')
#
# {Java} Lasta Di Only:
# o dbfluteDiXmlNamespace: (NotRequired - Default 'dbflute')
# o dbfluteDiXmlPackageName: (NotRequired - Default '../resources')
# o dbfluteDiXmlFileName: (NotRequired - Default 'dbflute.xml')

 Plugins are guaranteed to be provided the resources found in
 <<<plexus.core>>> and <<<plexus.core.maven>>> realms at run-time if required.
 Plugins can state compile-time dependencies on any of the resources found in
 the core realms listed above and these dependencies will be included in the
 plugin descriptor that is generated but when running within Maven these
 resources will be filtered out. In other words these resources will not

			},
			{
				"parallelizationMethod":{
					"name":"TestDistribution"
				},
				"subprojects":[
					"test-kit",
					"samples",
					"resources-sftp",
					"resources-s3",
					"resources-http",
					"resources-gcs",
					"resources",
					"reporting",
					"publish",
					"process-services",
					"problems-api"
				]
			},
			{
				"parallelizationMethod":{

  // the enumerated resources in any API group will be allowed. "" represents the core API group and "*" represents all API groups.
  // +optional
  repeated string apiGroups = 2;

  // Resources is a list of resources this rule applies to.  '*' represents all resources in the specified apiGroups.

  </properties>

  <build>
    <resources>
      <resource>
        <directory>.</directory>
        <includes>
          <include>pom.xml</include>
          <include>src/**</include>
        </includes>
      </resource>
      <resource>
        <directory>src/main/resources</directory>
      </resource>
    </resources>
  </build>

  </properties>

  <build>
    <resources>
      <resource>
        <directory>.</directory>
        <includes>
          <include>pom.xml</include>
          <include>src/**</include>
        </includes>
      </resource>
      <resource>
        <directory>src/main/resources</directory>
      </resource>
    </resources>
  </build>

Istio reads from over 20 different resources types, and aggregates them together to build the proxy configuration. These resources can be sourced from Kubernetes (via watches), files, or over xDS; Kubernetes is by far the most common usage, though.

Primarily for historical reasons, ingestion is split into a few components.

#### ConfigStore

  </dependencies>
  <build>
    <resources>
      <resource>
        <directory>..</directory>
        <includes>
          <include>LICENSE</include> <!-- copied from the parent pom because I couldn't figure out a way to make combine.children="append" work -->
          <include>proguard/*</include>
        </includes>
        <targetPath>META-INF</targetPath>
      </resource>
    </resources>
    <plugins>
      <plugin>

{
  "resources": [
    {"pattern": "okhttp3/internal/publicsuffix/publicsuffixes.gz"}
  ]

    istio.io/rev: {{ .Values.revision | default "default" }}
    install.operator.istio.io/owning-resource: {{ .Values.ownerName | default "unknown" }}
    operator.istio.io/component: "Cni"
rules:
  - apiGroups: [""]
    resources: ["events"]
    verbs: ["create", "patch"]
  - apiGroups: [""]
    resources: ["pods"]
    verbs: ["watch", "get", "list"]
{{- if .Values.cni.repair.repairPods }}