Version 2.2.1


Start date not set

Released: 11/Aug/09

Release Notes

Warnings indicate when the status of a JIRA issue doesn't reflect related development activity. For example: an issue marked complete that has an open pull request should be marked as still being in progress.

Unreviewed Code

These issues have been marked complete but the commits are not part of a pull request or review.

BlockerBugMNG-3506Custom ArtifactHandler not resolved for project when an additional plugin with extensions is defined in parent pomJohn CaseyClosed2 commits
BlockerBugMNG-4228[regression] Authorization failed: Not authorized by proxy.John CaseyClosed5 commits
BlockerBugMNG-4235[regression] Maven 2.2.0 produces invalid checksums during deployment to secured HTTP repoJohn CaseyClosed2 commits
BlockerImprovementMNG-4254Support selection of wagon implementation for a particular protocolJohn CaseyClosed6 commits
CriticalBugMNG-4270ArtifactHandler, LifecycleMapping from plugin dependency is not used when plugin extensions are enabledJohn CaseyClosed4 commits
MajorBugMNG-3265maven-model Extension.equals causes NPE when any field is uninitializedBenjamin BentmannClosed2 commits
MajorBugMNG-3753ArtifactResolverDiagnoser.diagnose() fails with NPE if nested IOException has no detail messageBenjamin BentmannClosed1 commit
MajorBugMNG-4189Maven not picking up specific timestamped version dependency when a later timestamped version was downloaded and already present in the local repositoryMaria Odea ChingClosed3 commits
MajorBugMNG-4238Custom ArtifactHandler provided by build extension isn't used for project artifactJohn CaseyClosed6 commits
MajorImprovementMNG-4279wagon provider selection should fail gracefully and use protocol for roleHint if protocol-provider roleHint isn't available.John CaseyClosed4 commits
MinorBugMNG-4275[regression] Direct relocations no longer log at WARNING level : MNG-3380 conflicts with MNG-1689John CaseyClosed4 commits
111 of 11