with the current POM.

      NOTE: This list will contain entries for repositories specified by ancestor POMs, including
      the default built-in super-POM, which is the parent of all POMs.
    ]]></description>
  </expression>
  <expression>
    <syntax>project.pluginArtifactRepositories</syntax>
    <configuration>
      <![CDATA[
<pluginRepositories>

        String message = exception.getMessage();

        assertTrue(
                message.contains("3 problems were encountered while processing the POMs (2 errors)"),
                "Message should contain problem count and error count");

        assertTrue(message.contains("[com.example:project1:1.0]"), "Message should contain project1 identifier");

 * Subclasses only differ in whether they save modifications to disk.
 *
 * <h2>Supported Upgrades</h2>
 *
 * <h3>Model Version Upgrades</h3>
 * <ul>
 *   <li><strong>4.0.0 → 4.1.0</strong>: Upgrades Maven 3.x POMs to Maven 4.1.0 format</li>
 * </ul>
 *
 * <h3>4.0.0 → 4.1.0 Upgrade Process</h3>
 * <ol>
 *   <li><strong>Namespace Update</strong>: Changes namespace from Maven 4.0.0 to 4.1.0 for all elements</li>

@Measurement(time = 10)
public class Xpp3DomPerfTest {
    @State(Scope.Benchmark)
    public static class AdditionState {
        List<Path> poms;

        @Setup(Level.Iteration)
        public void setUp() throws IOException {
            Path userHome = Paths.get(System.getProperty("user.home"));
            poms = Files.walk(userHome.resolve(".m2/repository/org/apache/maven"))
                    .filter(p -> p.getFileName().toString().endsWith(".pom"))

            assertTrue(duration < 5000, "Artifact computation should complete within 5 seconds for 100 POMs");

            // Verify correctness
            assertNotNull(gavs, "Artifact set should not be null");
            assertEquals(100, gavs.size(), "Should have computed GAVs for all 100 POMs");
        }
    }

tolerations](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/). This feature allows you to specify rules for "repelling" pods from nodes by default, which enables use cases like dedicated nodes and reserving nodes with special features for pods that need those features. We've also added a `NoExecute` taint type that evicts already-running pods, and an associated `tolerationSeconds` field to tolerations to delay the eviction for a specified amount of time. As before, taints are created...

- `LabelSelectors` specified in `topologySpreadConstraints` were validated to ensure that pods are scheduled as expected. Existing pods with invalid `LabelSelectors` could be updated, but new pods were required to specify valid `LabelSelectors`. ([#111802](https://github.com/kubernetes/kubernetes/pull/111802), [@maaoBit](https://github.com/maaoBit))

  * Stop 'kubectl drain' deleting pods with local storage.
  * Add `kubectl rollout status`
* Security/Auth
  * L7 LB controller and disk attach controllers run on master, so nodes do not need those privileges.
  * Setting TLS1.2 minimum
  * `kubectl create secret tls` command
  * Webhook Token Authenticator
  * **beta** PodSecurityPolicy objects limits use of security-sensitive features by pods.
* Kubectl

errors.invalid_query_sort_value = Le tri spécifié {0} n'est pas valide.
errors.invalid_query_unsupported_sort_field = Le tri spécifié {0} n'est pas pris en charge.
errors.invalid_query_unsupported_sort_order = L'ordre de tri spécifié {0} n'est pas pris en charge.
errors.invalid_query_cannot_process=Impossible de traiter la requête spécifiée.
errors.crud_invalid_mode = Le mode est incorrect. (pas {0}, mais {1})

    }

    private static String createMessage(List<ProjectBuildingResult> results) {
        if (results == null || results.isEmpty()) {
            return "Some problems were encountered while processing the POMs";
        }

        long totalProblems = 0;
        long errorProblems = 0;

        for (ProjectBuildingResult result : results) {
            List<ModelProblem> problems = result.getProblems();