if (classifier != null && !classifier.isEmpty()) {
                sb.append(" -Dclassifier=");
                sb.append(classifier);
            }
            sb.append(" -Dpackaging=");
            sb.append(type);
            sb.append(" -Dfile=/path/to/file");
            sb.append(LS);

            // If people want to deploy it
            sb.append(LS);

quarkus/extensions/caffeine/deployment/pom.xml
	quarkus/core/deployment/pom.xml
	quarkus/extensions/caffeine/runtime/pom.xml
	quarkus/extensions/vertx-http/dev-ui-spi/pom.xml
quarkus/integration-tests/packaging/pom.xml
	quarkus/extensions/resteasy-classic/resteasy/runtime/pom.xml
	quarkus/integration-tests/shared-library/pom.xml
	quarkus/test-framework/junit5-internal/pom.xml
quarkus/extensions/vertx-graphql/runtime/pom.xml

is widely used among developers working in that language.

  The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an

The AGPLv3 provides no obligation by any party to support, maintain, or warranty the original or any modified work.

#
#   Important for patching:
#
#   (2) This script targets any POSIX shell, so it avoids extensions provided
#       by Bash, Ksh, etc; in particular arrays are avoided.
#
#       The "traditional" practice of packing multiple parameters into a
#       space-separated string is a well documented source of bugs and security
#       problems, so this is (mostly) avoided, by progressively accumulating

  "durations" : [ {
    "testProject" : "archivePerformanceProject",
    "linux" : 170
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.corefeature.ArchiveTreePerformanceTest.packing tar",
  "durations" : [ {
    "testProject" : "archivePerformanceProject",
    "linux" : 164
  } ]
}, {

      "coverage" : {
        "per_commit" : [ "linux" ]
      }
    } ]
  }, {
    "testId" : "org.gradle.performance.regression.corefeature.ArchiveTreePerformanceTest.packing tar",
    "groups" : [ {
      "testProject" : "archivePerformanceProject",
      "coverage" : {
        "per_commit" : [ "linux" ]
      }
    } ]
  }, {

nfiguration/assign-pod-node/). Node affinity/anti-affinity allow you to specify rules for restricting which node(s) a pod can schedule onto, based on the labels on the node. Pod affinity/anti-affinity allow you to specify rules for spreading and packing pods relative to one another, across arbitrary topologies (node, zone, etc.) These affinity rules are now be specified in a new-in-1.6 `affinity` field of the PodSpec. Kubernetes 1.6 continues to support the alpha `scheduler.alpha.kubernetes.io/affinity`...