<<online>> status, or else doesn't care.

  * Otherwise, don't bind the mojo. Log a debug message to indicate that it is
    sensitive the online state of the application, and that this state is
    currently wrong for execution.

    <<NOTE:>> Do we want to fail when we cannot bind a mojo to the lifecycle
    because of offline/online status? That would probably indicate that the user

          <type>String</type>
        </field>
        <field>
          <name>outputDirectory</name>
          <version>4.0.0+</version>
          <description>
            The directory where compiled application classes are placed.
            The default value is {@code target/classes}.
          </description>
          <type>String</type>
        </field>
        <field>
          <name>testOutputDirectory</name>

    }

    @Test
    void testPropertiesNoDuplication() throws Exception {
        PomTestWrapper pom = buildPom("properties-no-duplication/sub");
        assertEquals(3, ((Properties) pom.getValue("properties")).size());
        assertEquals("child", pom.getValue("properties/pomProfile"));
    }

    @Test