You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Design Considerations: Refactoring Artifact Handling for Maven 2.1

Version Ranges

Need more information here about specific design problems with version ranges.

Artifact Identity

  1. Platform-specific Artifacts
  1. Encoding Build Options into Artifact Identity
  1. Alternative Versioning Schemes

Conflict Resolution

Currently, there is only one implementation of conflict resolution in Maven. In certain cases, users may wish to use alternative methods to resolve these conflicts, maybe even opting to fail the build when a conflict is detected.

These different resolution techniques may not be mapped 1:1 with a given POM. Instead, it may make more sense to allow the user to configure his own preferred strategy, in order to make his role in the development effort simpler. One such example might be QA testers, which may opt to verify that all dependencies are convergent before proceeding with what may be an irreproducible build.

Artifact Resolution

  1. Disabling Transitivity
  1. Refactoring Dependency Exclusions
  1. Refactoring Scopes
  1. Refactoring DependencyManagement Behavior

Specification Dependencies and Provides Notation

  • No labels