<mailingLists>
    <!--mailingList> MNG-3124: no way to add a list to parent content, only full override
      <name>child</name>
      <post>post@mailing.list.com</post>
      <subscribe>subscribe@mailing.list.com</subscribe>
      <unsubscribe>unsubscribe@mailing.list.com</unsubscribe>
    </mailingList-->
  </mailingLists>

  <build>
    <plugins>
      <plugin>
        <groupId>inheritance.configuration</groupId>

    void testAs_Object_Success() throws PACDecodingException {
        // Test successful casting
        String expected = "test string";
        Object obj = expected;
        String result = ASN1Util.as(String.class, obj);
        assertSame(expected, result);
    }

    @Test
    void testAs_Object_Failure() {
        // Test failed casting
        Object obj = 123; // Integer
        assertThrows(PACDecodingException.class, () -> {

  <url>http://www.apache.org/</url>

  <mailingLists>
    <mailingList>
      <name>parent</name>
      <post>post@mailing.list.com</post>
      <subscribe>subscribe@mailing.list.com</subscribe>
      <unsubscribe>unsubscribe@mailing.list.com</unsubscribe>
    </mailingList>
  </mailingLists>

  <build>
    <plugins>
      <plugin>
        <groupId>inheritance.configuration</groupId>

   * com.google.common.testing.junit3.TearDownTestCase} and {@code
   * com.google.common.testing.junit4.TearDownTestCase} for example.
   *
   * <p>A failing {@link TearDown} may or may not fail a tl4j test, depending on the version of
   * JUnit test case you are running under. To avoid failing in the face of an exception regardless
   * of JUnit version, implement a {@link SloppyTearDown} instead.
   *

    - [Server Binaries](#server-binaries-4)
    - [Node Binaries](#node-binaries-4)
  - [Changelog since v1.19.11](#changelog-since-v11911)
  - [Changes by Kind](#changes-by-kind-4)
    - [Feature](#feature-2)
    - [Failing Test](#failing-test)
    - [Bug or Regression](#bug-or-regression-3)
    - [Other (Cleanup or Flake)](#other-cleanup-or-flake-1)
  - [Dependencies](#dependencies-4)
    - [Added](#added-4)
    - [Changed](#changed-4)

  <mailingLists>
    <mailingList>
      <name>parent</name>
      <subscribe>subscribe@mailing.list.com</subscribe>
      <unsubscribe>unsubscribe@mailing.list.com</unsubscribe>
      <post>post@mailing.list.com</post>
    </mailingList>
  </mailingLists>

  <build>
    <plugins>
      <plugin>
        <groupId>inheritance.configuration</groupId>

---
name: Bug report
about: A reproducible problem
title: ''
labels: bug
assignees: ''

---

Good bug reports include a failing test! Writing a test helps you to isolate and describe the problem, and it helps us to fix it fast. Bug reports without a failing test or reproduction steps are likely to be closed.

Here’s an example test to get you started.

    - [Container Images](#container-images-10)
  - [Changelog since v1.26.4](#changelog-since-v1264)
  - [Changes by Kind](#changes-by-kind-10)
    - [API Change](#api-change-4)
    - [Feature](#feature-10)
    - [Failing Test](#failing-test)
    - [Bug or Regression](#bug-or-regression-10)
    - [Other (Cleanup or Flake)](#other-cleanup-or-flake-3)
  - [Dependencies](#dependencies-10)
    - [Added](#added-10)
    - [Changed](#changed-10)

  ----------

  Home Page:          https://maven.apache.org
  Downloads:          https://maven.apache.org/download.html
  Release Notes:      https://maven.apache.org/docs/history.html
  Mailing Lists:      https://maven.apache.org/mailing-lists.html
  Source Code:        https://gitbox.apache.org/repos/asf/maven.git
  Issue Tracking:     https://issues.apache.org/jira/browse/MNG

   * com.google.common.testing.junit3.TearDownTestCase} and {@code
   * com.google.common.testing.junit4.TearDownTestCase} for example.
   *
   * <p>A failing {@link TearDown} may or may not fail a tl4j test, depending on the version of
   * JUnit test case you are running under. To avoid failing in the face of an exception regardless
   * of JUnit version, implement a {@link SloppyTearDown} instead.
   *