-----
 2016-11-14
 -----

${project.name}

 ${project.description}

* Useful entry points

 * {{{./apidocs/org/apache/maven/cli/MavenCli.html}MavenCli.doMain(CliRequest)}} is the main method preparing runtime environment before running {{{../maven-core/}Maven.execute()}}

* References

 * {{{./cli.html}CLI options}},

 * {{{./logging.html}logging API}}.

      return "SynchronizedHelper";
    }
  }

  private static boolean mightBeAndroid() {
    String runtime = System.getProperty("java.runtime.name", "");
    // I have no reason to believe that `null` is possible here, but let's make sure we don't crash:
    return runtime == null || runtime.contains("Android");
  }

Java serialization is inherently Java-centric and does not support cross-language scenarios well.

- **Type Safety:**
Java serialization does not enforce type safety as strictly as some alternatives, potentially leading to runtime errors.

## Decision

We do not use Java serialization.
Instead, we use custom serialization where we explicitly describe how data objects should be serialized and deserialized.

    this.implied = copyToSet(implied);
  }

  @Override
  public Set<Feature<? super Map>> getImpliedFeatures() {
    return implied;
  }

  @Retention(RetentionPolicy.RUNTIME)
  @Inherited
  @TesterAnnotation
  public @interface Require {
    MapFeature[] value() default {};

    MapFeature[] absent() default {};
  }

This platform does not provide special support for a particular kind of automation. This is the responsibility of other platforms. 

It is made up of 3 architecture modules:

- **Runtime**: Provides the runtimes or "containers" in which code runs. These runtimes include the Gradle client, the daemon and the worker processes. This is the base module on which all other architecture modules depend.

 * interface.
 * @since 3.0.2
 */
public interface EventSpy {
    /**
     * Context
     */
    interface Context {

        /**
         * Gets key-value pairs providing information about the Maven runtime.
         *
         * @return The key-value pairs, never {@code null}.
         */
        Map<String, Object> getData();
    }

    /**
     * Initializes the spy.
     *

 */
@CacheableTask
public abstract class ExtractGradleApiInfoTask extends DefaultTask {

    private static final String GRADLE_API_INFO_JAR = "gradle-runtime-api-info";
    private static final String UPGRADED_PROPERTIES_FILE = "upgraded-properties.json";

    public ExtractGradleApiInfoTask() {
        getGradleApiInfoJarPrefix().convention(GRADLE_API_INFO_JAR);
    }

import javax.inject.Inject;
import java.io.File;

import static com.google.common.collect.Iterables.getOnlyElement;
import static java.util.stream.Collectors.toList;

/**
 * Extracts Kotlin DSL runtime generated sources.
 *
 * Current implementation extracts these from the wrapper's API jars.
 * This is not correct as it should do this with the built distribution instead.
 *

/**
 * Used if your Mojo needs to fork a <a href="/ref/3.0.4/maven-core/lifecycles.html">lifecycle</a>.
 *
 * @since 4.0.0
 */
@Experimental
@Documented
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@Inherited
public @interface Execute {
    /**
     * Lifecycle phase to fork. Note that specifying a phase overrides specifying a goal.
     * @return the phase
     */
    @Nonnull

When working on some source code it is important to be aware of the runtimes in which it will run, so that you don't break these constraints.
There is some assistance in the IDE for this plus a lot of validation that is applied at build time and on CI, but it is useful to keep these constraints in mind as well.

See [Gradle runtimes](runtimes.md) for a list of these runtimes and more details.

### Build execution model