import java.util.Set;

import org.apache.maven.model.Plugin;

/**
 * @since 3.0
 */
public interface LifeCyclePluginAnalyzer {
    Set<Plugin> getPluginsBoundByDefaultToAllLifecycles(String packaging);

# For release jobs, we will pin these on the release branch
keras-nightly ~= 3.0.0.dev
tb-nightly ~= 2.19.0.a
# Test dependencies
grpcio >= 1.24.3, < 2.0
portpicker == 1.6.0
scipy >= 1.13.0
requests >= 2.31.0
packaging==23.2
setuptools==70.0.0
jax==0.4.7
# The dependencies below are needed for TF wheel testing.
tensorflow-io-gcs-filesystem==0.37.1
libclang >= 13.0.0
google_pasta ~= 0.2

 * </ul>
 *
 * <p>For the main artifact and attached artifacts, the
 * {@link org.apache.maven.api.services.ArtifactManager ArtifactManager} service must be used
 * to point the artifact to a {@link Path} during the packaging phase.</p>
 *
 * @since 4.0.0
 * @see Project#getMainArtifact()
 * @see Project#getPomArtifact()
 * @see org.apache.maven.api.services.ProjectManager#attachArtifact(Session, Project, Path)

  <parent>
    <groupId>com.google.guava</groupId>
    <artifactId>guava-parent</artifactId>
    <version>HEAD-android-SNAPSHOT</version>
  </parent>
  <artifactId>guava</artifactId>
  <packaging>bundle</packaging>
  <name>Guava: Google Core Libraries for Java</name>
  <url>https://github.com/google/guava</url>
  <description>
    Guava is a suite of core and expanded libraries that include

            String classifier,
            String scope,
            String inheritedScope,
            boolean optional);

    Artifact createBuildArtifact(String groupId, String artifactId, String version, String packaging);

    Artifact createProjectArtifact(String groupId, String artifactId, String version);

    Artifact createParentArtifact(String groupId, String artifactId, String version);

 * failing tasks only, to not use up unnecessary disk space on Team City. This also improves the performance of
 * artifact publishing by reducing the artifacts and packaging reports that consist of multiple files.
 *
 * Reducing the number of reports also makes it easier to find the important ones when analysing a failed build in
 * Team City.
 */

                new ArtifactRepositoryPolicy());
    }

    @Override
    public Artifact createArtifact(String groupId, String artifactId, String version, String packaging) {
        return createArtifact(groupId, artifactId, version, null, packaging);
    }

    @Override
    public Artifact createArtifact(String groupId, String artifactId, String version, String scope, String type) {

We have a lifecycle mapping for the packaging of *jar* below. You see that for this packaging we have a *default* lifecycle and a list of phases where each phase is a comma separated list of goals to run and they are in the form groupId:artifactId:version.

<configuration>
  <lifecycles>
    <lifecycle>
      <id>default</id>
      <phases>
        <process-resources>org.apache.maven.plugins:maven-resources-plugin:resources</process-resources>

h4. Generation of plugin metadata and packaging

To create the packaging for a plugin a special Maven packaging would be created with an accompanying life-cycle in order to create the plugin metadata required and create an archive of the plugin that can be consumed at runtime.

	<modelVersion>4.0.0</modelVersion>
	<artifactId>fess-crawler</artifactId>
	<packaging>jar</packaging>
	<name>Fess Crawler</name>
	<description>Fess Crawler is a crawler framework.</description>
	<parent>
		<groupId>org.codelibs.fess</groupId>
		<artifactId>fess-crawler-parent</artifactId>