// than the CPU profiler when filtered to this goroutine via labels.
		cpuHogger(cpuHog1, &salt1, dur)
	}()

	trace.Stop()
	pprof.StopCPUProfile()

	// Summarize the CPU profile to stderr so the test can check against it.

	prof, err := profile.Parse(cpuBuf)
	if err != nil {
		log.Fatalf("failed to parse CPU profile: %v", err)
	}

Gradle lets us know the outcome of each task in the console output:

- `FROM-CACHE` - tasks have been fetched from the local build cache.
- `UP-TO-DATE` - tasks that used incremental build and were not re-run.

To summarize:

1. First, we used the `build` task to populate our local cache with task inputs and outputs -- we can imagine this was done a week ago.

 */
package org.apache.maven.execution;

import java.util.Objects;

import org.apache.maven.project.MavenProject;

/**
 * Summarizes the result of a project build in the reactor.
 *
 */
public abstract class BuildSummary {

    /**
     * The project being summarized.
     */
    private final MavenProject project;

    /**
     * The build time of the project in milliseconds.
     */

package org.apache.maven.execution;

import org.apache.maven.project.MavenProject;

/**
 * Summarizes the result of a successful project build in the reactor.
 *
 */
public class BuildSuccess extends BuildSummary {

    /**
     * Creates a new build summary for the specified project.
     *
     * @param project The project being summarized, must not be {@code null}.
     * @param time The build time of the project in milliseconds.

/**
 * Summarizes the result of a failed project build in the reactor.
 *
 */
public class BuildFailure extends BuildSummary {

    /**
     * The cause of the build failure.
     */
    private final Throwable cause;

    /**
     * Creates a new build summary for the specified project.
     *
     * @param project The project being summarized, must not be {@code null}.

// See the License for the specific language governing permissions and
// limitations under the License.

[[version-catalog-problems]]
= Troubleshooting version catalog problems

This page summarizes the different problems that Gradle reports when using version catalogs and provides guidance for fixing them.

[[accessor_name_clash]]
== Accessor name clash

Gradle does its best to map Gradle-specific concepts to Maven or Ivy.
When a build file uses features that can only be represented in Gradle Module Metadata, Gradle will warn you at publication time.
The table below summarizes how some Gradle specific features are mapped to Maven and Ivy:

.Mapping of Gradle specific concepts to Maven and Ivy
|===
|Gradle|Maven|Ivy|Description