under the License.
-->

<project>
    <modelVersion>4.0.0</modelVersion>
    <artifactId>aid</artifactId>
    <groupId>gid</groupId>
    <version>0.1</version>
    <packaging>pom</packaging>

    <profiles>
        <profile>
            <id>+invalid-id</id>
        </profile>
        <profile>
            <id>-invalid-id</id>
        </profile>
        <profile>
            <id>!invalid-id</id>

  <modelVersion>4.0.0</modelVersion>
  <artifactId>aid</artifactId>
  <groupId>gid</groupId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <profiles>

    <profile>
      <id>property-name-project-version</id>
      <activation>
        <property>
          <name>${project.version}</name>
        </property>
      </activation>
    </profile>

        <artifactId>duplicate</artifactId>
      </plugin>
      <plugin>
        <groupId>test</groupId>
        <artifactId>duplicate</artifactId>
      </plugin>
    </plugins>
  </build>

  <profiles>
    <profile>
      <id>test</id>
      <build>
        <pluginManagement>
          <plugins>
            <plugin>
              <groupId>profile</groupId>

  <modelVersion>4.0.0</modelVersion>
  <artifactId>aid</artifactId>
  <groupId>gid</groupId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <profiles>

    <profile>
      <id>exists-project-version</id>
      <activation>
        <file>
          <exists>${project.version}/test.txt</exists>
        </file>
      </activation>
    </profile>

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

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

        return this;
    }

    @Override
    public List<String> getActiveProfileIds() {
        return request.getActiveProfileIds();
    }

    @Override

  <modelVersion>4.0.0</modelVersion>
  <artifactId>aid</artifactId>
  <groupId>gid</groupId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <profiles>
    <profile>
      <id>exists-basedir</id>
      <activation>
        <file>
          <exists>${basedir}/test.txt</exists>
        </file>
      </activation>
    </profile>
    <profile>

both the charts and configuration profiles can come from three different sources: compiled-in, local filesystem.
The source may be selected independently for the charts and profiles. The different steps in creating the manifest are
as follows:

1. The user CR (my_custom.yaml) selects a configuration profile. If no profile is selected, the
[default profile](../manifests/profiles/default.yaml) is used. Each profile is defined as a

          </execution>
          <execution>
            <id>a</id>
            <phase>test</phase>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

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

            <phase>site</phase>
            <goals><goal>javadoc</goal></goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
  <profiles>
    <profile>
        <id>sonatype-oss-release</id>
        <build>
          <plugins>
            <plugin>
              <artifactId>maven-gpg-plugin</artifactId>
              <version>3.0.1</version>

                return true;
            }
        });

        List<Profile> profiles = Collections.singletonList(newProfile("one"));
        DefaultProfileActivationContext context = new DefaultProfileActivationContext();
        SimpleProblemCollector problems = new SimpleProblemCollector();
        List<Profile> active = selector.getActiveProfiles(profiles, context, problems);
        assertTrue(active.isEmpty());