}

    protected String getJdkVersion() {
        return JDK_VERSION;
    }

    @Override
    protected boolean canDetectActivation(Profile profile) {
        return profile.getActivation() != null
                && profile.getActivation().getJdk() != null
                && !profile.getActivation().getJdk().isEmpty();
    }

Kazushi Morishima <******@****.***> 1536732811 +0900

    <module>maven-api-spi</module>
    <module>maven-api-cli</module>
  </modules>

  <properties>
    <project.directory>api</project.directory>
  </properties>

  <profiles>
    <profile>
      <id>reporting</id>
      <reporting>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-javadoc-plugin</artifactId>

    @Override
    public boolean canDetermineActivation(Profile profile) {
        Activation activation = profile.getActivation();
        return activation != null && activation.getOs() != null;
    }

    @Override
    public boolean isActive(Profile profile) {
        Activation activation = profile.getActivation();
        ActivationOS os = activation.getOs();

            <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>

            /*
             * MNG-4900: Hack to workaround deficiency of legacy API which makes it impossible for plugins to access the
             * global profile manager which is required to build a POM like a CLI invocation does. Failure to consider
             * the activated profiles can cause repo declarations to be lost which in turn will result in artifact

      But it's always weird that published poms reference test-only libraries at all, so I'm not in any rush to do so.
      -->
    </dependencies>
  </dependencyManagement>
  <profiles>
    <profile>
      <id>sonatype-oss-release</id>
      <build>
        <plugins>
          <plugin>
            <artifactId>maven-gpg-plugin</artifactId>
            <version>3.0.1</version>

      But it's always weird that published poms reference test-only libraries at all, so I'm not in any rush to do so.
      -->
    </dependencies>
  </dependencyManagement>
  <profiles>
    <profile>
      <id>sonatype-oss-release</id>
      <build>
        <plugins>
          <plugin>
            <artifactId>maven-gpg-plugin</artifactId>
            <version>3.0.1</version>

          <description>The identifier of this build profile. This is used for command line
            activation, and identifies profiles to be merged.
          </description>
        </field>
        <field>
          <name>activation</name>
          <version>4.0.0+</version>
          <description>The conditional logic which will automatically trigger the inclusion of this
            profile.</description>
          <association>

							<em class="fa fa-arrow-circle-left">
							<la:message key="labels.profile.back" />
						</la:link>
						<button type="submit" name="changePassword"
							class="btn btn-success"
							value="<la:message key="labels.profile.update"/>">
							<em class="fa fa-pencil-alt">
							<la:message key="labels.profile.update" />
						</button>
					</div>
				</la:form>
			</div>
		</div>
	</div>