9763ef7c5d
Maven 2.2.1 aims to correct several critical regressions related to the selection of the HttpClient-based Wagon implementation for HTTP/HTTPS transfers in Maven 2.2.0. The new release reverts this selection, reinstating the Sun-based - or lightweight - Wagon implementation as the default for this sort of traffic. However, Maven 2.2.1 goes a step further to provide a means of selecting which provider - or implementation - the user wishes to use for a particular transfer protocol. More information on providers can be found in our Guide to Wagon Providers. In addition, Maven 2.2.1 addresses some long-standing problems related to injecting custom lifecycle mappings and artifact handlers. These custom components are now correctly loaded regardless of whether they come from a plugin with the extensions flag enabled, or from a pure build extension. In addition, custom artifact handlers now will be used to configure the attributes of the main project artifact in addition to any artifacts related to dependencies or project attachments created during the build.
7 lines
395 B
Text
7 lines
395 B
Text
$NetBSD: distinfo,v 1.4 2009/11/07 00:14:53 yyamano Exp $
|
|
|
|
SHA1 (apache-maven-2.2.1-bin.tar.bz2) = 47ac0417a200cbc6d1b967d6b7c6ae1138e9e3e0
|
|
RMD160 (apache-maven-2.2.1-bin.tar.bz2) = 25d523d3dc86cf4695b0e343cf0f6e58ea8a54e3
|
|
Size (apache-maven-2.2.1-bin.tar.bz2) = 2839688 bytes
|
|
SHA1 (patch-aa) = 74c4607226b3d783648c4fc369460dcce4a0144f
|
|
SHA1 (patch-ab) = d9219f96473c4a929cad15990e1c131e08f8ed13
|