@Override
    @BeforeEach
    void setUp() throws Exception {
        activator = new JdkVersionProfileActivator();
    }

    private Profile newProfile(String jdkVersion) {
        Activation a = Activation.newBuilder().jdk(jdkVersion).build();

        Profile p = Profile.newBuilder().activation(a).build();

        return p;
    }

    private Properties newProperties(String javaVersion) {

        </executions>
      </plugin>
    </plugins>
  </build>

  <profiles>
    <profile>
      <id>create-distribution-in-dir</id>
      <activation>
        <property>
          <name>distributionTargetDir</name>
        </property>
      </activation>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>

    }

    public List<String> getGoals() {
        return request.getGoals();
    }

    /**
     * Gets the user properties to use for interpolation and profile activation. The user properties have been
     * configured directly by the user on his discretion, e.g. via the {@code -Dkey=value} parameter on the command
     * line.
     *
     * @return The user properties, never {@code null}.

     * @param id The identifier of the profile.
     */
    public void deactivateOptionalProfile(String id) {
        this.activations.put(id, ActivationSettings.deactivatedOpt());
    }

    /**
     * Adds a profile activation to the request.
     * @param id The identifier of the profile.
     * @param active Should the profile be activated?

					<artifactId>cxf-rt-rs-client</artifactId>
				</exclusion>
				<exclusion>
					<groupId>javax.activation</groupId>
					<artifactId>javax.activation-api</artifactId>
				</exclusion>
				<exclusion>
					<groupId>javax.activation</groupId>
					<artifactId>activation</artifactId>
				</exclusion>
				<exclusion>
					<groupId>com.intellij</groupId>

    </profile>
    <profile>
      <id>suppress-open-jre-modules-for-toolchain-1.8</id>
      <activation>
        <property>
          <name>surefire.toolchain.version</name>
          <!-- the value provided by java.specification.version -->
          <value>1.8</value>
        </property>
      </activation>
      <properties>
        <test.add.opens></test.add.opens>
      </properties>
    </profile>

              <!--              <exclude>org.apache.maven.model.profile.activation.FileProfileActivator#setProfileActivationFilePathInterpolator(org.apache.maven.model.path.ProfileActivationFilePathInterpolator):METHOD_REMOVED</exclude>-->
              <!--              <exclude>org.apache.maven.model.profile.activation.FileProfileActivator#FileProfileActivator():CONSTRUCTOR_REMOVED</exclude>-->

      </description>
      <fields>
        <field>
          <name>activation</name>
          <version>1.0.0+</version>
          <description>
            The conditional logic which will automatically trigger the inclusion of this profile.
          </description>
          <association>
            <type>Activation</type>
          </association>
        </field>
        <field>

* installation
* activation
* update
* deactivation
* un-installation

When a plugin is installed we may want to check the license and make users agree. We may also want to unpack the given plugin in a particular location.

            <p>In addition to the traditional activation mechanisms (JDK version, OS properties,
            file existence, etc.), Maven now supports a powerful condition-based activation
            through the {@code condition} field. This new mechanism allows for more flexible
            and expressive profile activation rules.</p>

            <h2>Condition Syntax</h2>