Hi everyone,
We've spent a little time talking about whether the next release should
be 2.1.1 or 2.2. This has mainly played out around the issue of MNG-4140
and whether or not to require JDK 1.5 for the next release. We had
settled on a solution for 2.1.1 that allowed Maven to continue operating
without version interpolation when used with JDK < 1.5.
However, there is another issue that I feel is important to address:
MNG-4147. This issue is caused by Sun's HTTPURLConnection implementation
- at least, in JDK 1.5 - which is used by the lightweight http wagon.
We're already bundling httpclient in Maven for use by the jackrabbit
webdav wagon, so it seems like a natural move to simply discontinue use
of the lightweight http wagon in favor of the httpclient-based one.
I feel like these are both very important issues to address, but one
carries a requirement for JDK 1.5+ in order to work (for JDK < 1.5, it
won't work even as well as it did in 2.1.0); the other carries quite a
bit of risk with it, since the httpclient-based wagon isn't in
production use anywhere AFAIK, and may contain subtle bugs as a result.
I'm not sure even a protracted RC process will flush out all the bugs if
we were to switch.
So, I propose the following: we should do a very tightly focused 2.2.0
release next, and forget 2.1.1. I know I was against this approach
before, mainly because I was concerned about scope-creep for that
release...but I'm not sure a 2.1.1 release will really be compelling
without at least attempting to solve the aforementioned problems.
I'd love to hear what others think.
-john
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
