maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r803251 - in /maven/site/trunk: pom.xml src/site/apt/guides/mini/guide-http-settings.apt src/site/apt/release-notes.apt.vm src/site/xdoc/index.xml.vm
Date Tue, 11 Aug 2009 19:25:34 GMT
Author: jdcasey
Date: Tue Aug 11 19:25:34 2009
New Revision: 803251

Update to 2.2.1


Modified: maven/site/trunk/pom.xml
--- maven/site/trunk/pom.xml (original)
+++ maven/site/trunk/pom.xml Tue Aug 11 19:25:34 2009
@@ -269,7 +269,7 @@
-    <current22xVersion>2.2.0</current22xVersion>
+    <current22xVersion>2.2.1</current22xVersion>

Modified: maven/site/trunk/src/site/apt/guides/mini/guide-http-settings.apt
--- maven/site/trunk/src/site/apt/guides/mini/guide-http-settings.apt (original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-http-settings.apt Tue Aug 11 19:25:34
@@ -1,16 +1,34 @@
-  Guide to HTTP Wagon Configuration
+  Guide to Advanced HTTP Wagon Configuration
   John Casey
   22 June 2009
-Configuring the HTTP Wagon
+Advanced Configuration of the HttpClient HTTP Wagon
-  <<NOTE:>> This feature is available in <<Maven 2.2.0>> and later.
+*Notice on Maven Versioning and Availability
-  Since the introduction of the HttpClient\[1\]-based HTTP Wagon as the default for Maven
2.2.0 and above, you have a lot more control over the
+**Maven 2.2.0
+  Starting in <<Maven 2.2.0>>, the HttpClient wagon was the implementation in
use. The remainder of this document
+  deals specifically with the differences between the HttpClient- and Sun-based HTTP wagons.
+**Maven 2.2.1
+  Due to several critical issues introduced by the HttpClient-based HTTP wagon, <<Maven
2.2.1>> reverted back to 
+  the Sun implementation (a.k.a. 'lightweight') of the HTTP wagon as the default for HTTP/HTTPS
+  The issues with the HttpClient-based wagon were mainly related to checksums, transfer timeouts,
and NTLM proxies,
+  and served as the primary cause for the release of <<2.2.1>> in the first place.
+  <<However>>, starting in <<Maven 2.2.1>> you have a choice: you
can use the default wagon implementation for a given
+  protocol, or you can select an alternative wagon <<<provider>>> you'd
like to use on a per-protocol basis. 
+  For more information, see the {{{}Guide
to Wagon Providers}} \[3\].
+  Using the HttpClient-based HTTP wagon, you have a lot more control over the
   configuration used to access HTTP-based Maven repositories. For starters, you have fine-grained
control over what HTTP headers
   are used when resolving artifacts. In addition, you can also configure a wide range of
parameters to control the behavior
   of HttpClient itself. Best of all, you have the ability to control these headers and parameters
for all requests, or individual 
@@ -344,4 +362,6 @@
     [[2]] {{{}HttpClient preference
architecture and configuration guide}}
+    [[3]] {{{}Guide to Wagon

Modified: maven/site/trunk/src/site/apt/release-notes.apt.vm
--- maven/site/trunk/src/site/apt/release-notes.apt.vm (original)
+++ maven/site/trunk/src/site/apt/release-notes.apt.vm Tue Aug 11 19:25:34 2009
@@ -46,6 +46,42 @@
     * the web site: {{}}
     * the maven-user mailing list: {{}}
+* 2.2.1 Release Notes
+  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.
+  The full list of changes can be found in our {{{}issue
management system}}, and is reproduced below.
+**Complete list of issues fixed in 2.2.1
+*** Bug
+      * MNG-3265 - maven-model Extension.equals causes NPE when any field is uninitialized
+      * MNG-3506 - Custom ArtifactHandler not resolved for project when an additional plugin
with extensions is defined in parent pom
+      * MNG-3753 - ArtifactResolverDiagnoser.diagnose() fails with NPE if nested IOException
has no detail message
+      * MNG-4189 - Maven not picking up specific timestamped version dependency when a later
timestamped version was downloaded and already present in the local repository
+      * MNG-4218 - NPE in AbstractArtifactResolutionException if DefaultArtifactResolver.resolveTransitively
is interrupted
+      * MNG-4228 - [regression] Authorization failed: Not authorized by proxy.
+      * MNG-4235 - [regression] Maven 2.2.0 produces invalid checksums during deployment
to secured HTTP repo
+      * MNG-4236 - [regression] http wagon uploads files twice with Maven 2.2.0 when preemptive
auth is disabled (default setting)
+      * MNG-4238 - Custom ArtifactHandler provided by build extension isn't used for project
+      * MNG-4240 - Direct dependencies with scope == provided will not have their transitive
dependencies resolved for compiling and testing
+      * MNG-4270 - ArtifactHandler, LifecycleMapping from plugin dependency is not used when
plugin extensions are enabled
+      * MNG-4275 - [regression] Direct relocations no longer log at WARNING level : MNG-3380
conflicts with MNG-1689
+*** Improvement
+      * MNG-4254 - Support selection of wagon implementation for a particular protocol
+      * MNG-4279 - wagon provider selection should fail gracefully and use protocol for roleHint
if protocol-provider roleHint isn't available.
+*** Task
+      * MNG-4290 - Update guide-http-settings to reflect the fact that sun-based http has
been restored as the default for the http/s wagons.
 * 2.2.0 Release Notes

Modified: maven/site/trunk/src/site/xdoc/index.xml.vm
--- maven/site/trunk/src/site/xdoc/index.xml.vm (original)
+++ maven/site/trunk/src/site/xdoc/index.xml.vm Tue Aug 11 19:25:34 2009
@@ -39,7 +39,7 @@
 <!-- Google CSE Search Box Ends -->
       <h5>Get Maven ${current22xVersion}</h5>
-      <span style="display: block; text-align: right; font-size: smaller">Released:
30 June 2009</span>
+      <span style="display: block; text-align: right; font-size: smaller">Released:
11 August 2009</span>
         <a href="download.html">
           <img src="images/folder-open.gif" border="0" alt="" title="Download Maven ${current22xVersion}"/>

View raw message