@Singleton
public class StrategyOrchestrator {

    private final List<UpgradeStrategy> strategies;

    @Inject
    public StrategyOrchestrator(List<UpgradeStrategy> strategies) {
        // DI container automatically sorts strategies by priority (highest first)
        this.strategies = strategies;
    }

    /**
     * Executes all applicable upgrade strategies in priority order.
     * Each strategy is checked for applicability before execution.

        @Test
        @DisplayName("should execute all applicable strategies")
        void shouldExecuteAllApplicableStrategies() throws Exception {
            UpgradeContext context = createMockContext();
            Map<Path, Document> pomMap = Map.of(Paths.get("pom.xml"), mock(Document.class));

            // Mock all strategies as applicable
            for (UpgradeStrategy strategy : mockStrategies) {

 * under the License.
 */

/**
 * Maven Upgrade Tool Goals and Strategies.
 *
 * <p>This package contains the implementation of the Maven upgrade tool (mvnup) that helps
 * upgrade Maven projects to be compatible with Maven 4. The tool is organized around
 * a goal-based architecture with pluggable upgrade strategies.</p>
 *
 * <h2>Architecture Overview</h2>
 *
 * <h3>Goals</h3>
 * <ul>

This is in contrast to the **development** stages, where you are constantly changing the code, breaking it and fixing it, stopping and restarting the development server, etc.

## Deployment Strategies { #deployment-strategies }

There are several ways to do it depending on your specific use case and the tools that you use.

import junit.framework.TestSuite;
import org.jspecify.annotations.NullUnmarked;

/**
 * Tests our AtomicHelper fallback strategies in AbstractFuture.
 *
 * <p>On different platforms AbstractFuture uses different strategies for its core synchronization
 * primitives. The strategies are all implemented as subtypes of AtomicHelper and the strategy is

 *
 * <p>On different platforms AggregateFutureState uses different strategies for its core
 * synchronization primitives. The strategies are all implemented as subtypes of AtomicHelper and
 * the strategy is selected in the static initializer of AggregateFutureState. This is convenient
 * and performant but introduces some testing difficulties. This test exercises the two fallback
 * strategies.
 *
 * <ul>

    }

    @Test
    void testLoadBalancingStrategies() throws Exception {
        // Test different load balancing strategies
        ChannelLoadBalancer loadBalancer = new ChannelLoadBalancer(channelManager);

        // Test setting different strategies
        LoadBalancingStrategy[] strategies = { LoadBalancingStrategy.ROUND_ROBIN, LoadBalancingStrategy.LEAST_LOADED,

import java.util.HashSet;
import java.util.Set;

/**
 * Result of an upgrade strategy application.
 * Uses sets of paths to track which POMs were processed, modified, or had errors,
 * avoiding double-counting when multiple strategies affect the same POMs.
 *
 * @param processedPoms the set of POMs that were processed
 * @param modifiedPoms the set of POMs that were modified
 * @param errorPoms the set of POMs that had errors
 */

/**
 * Strategy interface for different types of upgrade operations.
 * Each strategy handles a specific aspect of the Maven upgrade process.
 *
 * <p>Strategies work with domtrip Documents for perfect formatting preservation.
 * Individual strategies can create domtrip Editors from Documents as needed:
 * <pre>
 * Editor editor = new Editor(document);
 * // ... perform domtrip operations ...

        List<UpgradeStrategy> strategies = List.of(
                new ModelUpgradeStrategy(),
                new CompatibilityFixStrategy(),
                new PluginUpgradeStrategy(),
                new InferenceStrategy());

        StrategyOrchestrator orchestrator = new StrategyOrchestrator(strategies);
        applyGoal = new Apply(orchestrator);