List<String> dependents = sorter.getDependents(id);

            if (dependents != null && !dependents.isEmpty()) {
                for (String dependentId : dependents) {
                    if (!buildSuccessesByProject.containsKey(dependentId)
                            && !buildFailuresByProject.containsKey(dependentId)) {
                        blackList(dependentId);
                    }
                }

     */
    @Nonnull
    Optional<Boolean> alsoMake();

    /**
     * Indicates whether Maven should also build the specified projects' dependents.
     *
     * @return an {@link Optional} containing true if dependents should also be built, false if not, or empty if not specified
     */
    @Nonnull
    Optional<Boolean> alsoMakeDependents();

    /**

## Segunda dependência, "dependable" e "dependente" { #second-dependency-dependable-and-dependant }

Então, você pode criar uma outra função para uma dependência (um "dependable") que ao mesmo tempo declara sua própria dependência (o que faz dela um "dependente" também):

{* ../../docs_src/dependencies/tutorial005_an_py310.py hl[13] *}

Vamos focar nos parâmetros declarados:

 *
 * @since 4.0.0
 */
@Experimental
@Immutable
public interface Dependency extends Artifact {
    /**
     * {@return the type of the dependency}.
     * A dependency can be a <abbr>JAR</abbr> file,
     * a modular-<abbr>JAR</abbr> if it is intended to be placed on the module path,
     * a <abbr>JAR</abbr> containing test classes, <i>etc.</i>

This is quite simple (not very useful), but will help us focus on how the sub-dependencies work.

## Second dependency, "dependable" and "dependant" { #second-dependency-dependable-and-dependant }

Then you can create another dependency function (a "dependable") that at the same time declares a dependency of its own (so it is a "dependant" too):

{* ../../docs_src/dependencies/tutorial005_an_py310.py hl[13] *}

Let's focus on the parameters declared:

  <modelVersion>4.0.0</modelVersion>

  <groupId>ut.simple</groupId>
  <artifactId>dependency</artifactId>
  <version>1.0</version>

  <name>Simple Unit Test Dependency</name>

## Segunda dependencia, "dependable" y "dependant" { #second-dependency-dependable-and-dependant }

Luego puedes crear otra función de dependencia (un "dependable") que al mismo tiempo declare una dependencia propia (por lo que también es un "dependant"):

{* ../../docs_src/dependencies/tutorial005_an_py310.py hl[13] *}

Centrémonos en los parámetros declarados:

~~ KIND, either express or implied.  See the License for the
~~ specific language governing permissions and limitations
~~ under the License.

 ---
 Default Dependency Types
 ---
 Hervé Boutemy
 ---
 2024-04-02
 ---

Default Dependency Types Reference

  Defined in <<<DefaultTypeProvider>>>
  ({{{./apidocs/org/apache/maven/repository/internal/type/DefaultTypeProvider.html}javadoc}},

      <scope>runtime</scope>
    </dependency>
    <dependency>
      <groupId>test</groupId>
      <artifactId>d</artifactId>
      <version>0.2</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>test</groupId>
      <artifactId>e</artifactId>
      <version>0.2</version>
      <scope>provided</scope>
    </dependency>
    <dependency>
      <groupId>test</groupId>

        <dependencies>
          <dependency>
            <groupId>test</groupId>
            <artifactId>a</artifactId>
            <version>0.2</version>
          </dependency>
          <dependency>
            <groupId>test</groupId>
            <artifactId>b</artifactId>
            <version>0.2</version>
            <scope>compile</scope>
          </dependency>
          <dependency>