*/
    @Nonnull
    Collection<Profile> getProfiles();

    /**
     * List of profile ids that have been explicitly activated by the user.
     */
    @Nonnull
    List<String> getActiveProfileIds();

    /**
     * List of profile ids that have been explicitly deactivated by the user.
     */
    @Nonnull

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

  <profiles>
    <profile>
      <id>test</id>
      <build>
        <pluginManagement>
          <plugins>
            <plugin>
              <groupId>profile</groupId>
              <artifactId>managed-plugin</artifactId>
              <executions>
                <execution>
                  <id>b</id>

    /**
     * Gets the file model to build (with profile activation).
     * If not set, model source will be used to load file model.
     *
     * @return The file model to build or {@code null} if not set.
     * @since 4.0.0
     */
    Model getFileModel();

    /**
     * Set the file model with profile activation
     *
     * @param fileModel

     | to accomplish, particularly when you only have a list of profile id's for debug.
     |
     | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
    <profile>
      <id>jdk-1.4</id>

      <activation>
        <jdk>1.4</jdk>
      </activation>

      <repositories>

            Set<String> profileIds = new HashSet<>();

            for (Profile profile : m.getProfiles()) {
                String prefix = "profiles.profile[" + profile.getId() + "].";

                validateProfileId(prefix, "id", problems, Severity.ERROR, Version.V40, profile.getId(), null, m);

                if (!profileIds.add(profile.getId())) {
                    addViolation(
                            problems,

  <properties>
    <!--
    We could override this to change which version we run tests under.
    However, I think that our -Djava.security.manager=allow profile is based on the *Maven* JDK.
    If we want to use overrides here, we should change that profile to also be based on surefire.toolchain.version.
    -->
    <surefire.toolchain.version>${java.specification.version}</surefire.toolchain.version>

  <properties>
    <!--
    We could override this to change which version we run tests under.
    However, I think that our -Djava.security.manager=allow profile is based on the *Maven* JDK.
    If we want to use overrides here, we should change that profile to also be based on surefire.toolchain.version.
    -->
    <surefire.toolchain.version>${java.specification.version}</surefire.toolchain.version>

     * from the runtime environment like {@link System#getProperties()} and environment variables.
     *
     * @return The execution properties, never {@code null}.
     */
    Map<String, String> getSystemProperties();

    /**
     * Gets the user properties to use for interpolation and profile activation. The user properties have been

        request.setLocationTracking(locationTracking);

        return this;
    }

    @Override
    public List<Profile> getProfiles() {
        return request.getProfiles();
    }

    @Override
    public FilterModelBuildingRequest setProfiles(List<Profile> profiles) {
        request.setProfiles(profiles);

        return this;
    }

    @Override

        return this;
    }

    @Override
    public List<Profile> getProfiles() {
        if (profiles == null) {
            profiles = new ArrayList<>();
        }

        return profiles;
    }

    @Override
    public DefaultModelBuildingRequest setProfiles(List<Profile> profiles) {
        if (profiles != null) {
            this.profiles = new ArrayList<>(profiles);