Fixing flaky test in TestCopyDependenciesMojo

[mihirgune]

Description

This Pull Request addresses test flakiness in the following test:

org.apache.maven.plugins.dependency.fromDependencies.TestCopyDependenciesMojo#testGetDependencies

Problem

The test performs a String equality check on the content of dependencies stored in mojo.resolvedDependencies against dependencies resolved through mojo.getDependencySets(true).getResolvedDependencies().

Since these dependencies are stored in java.util.Set collections, their ordering is non-deterministic, which occasionally causes test failures when executed with the Nondex plugin.

Solution

To address this, I modified the test to verify that the sets contain the same elements, regardless of order.

I've changed the assertion from:

assertEquals(
    mojo.getResolvedDependencies(true).toString(),
    mojo.getDependencySets(true).getResolvedDependencies().toString()
);

to

assertTrue(
    mojo.getResolvedDependencies(true).containsAll(
        mojo.getDependencySets(true).getResolvedDependencies()
    )
);

This ensures the test passes as long as both sets contain the same dependencies, regardless of order.

I'd appreciate any feedback on this approach and am open to making further adjustments if necessary.

• I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004