Merge fails, need some rework to match trunk changes
would be simpler to deprecate and drop this shit out from repository as we
did for wagon-webdav

2011/8/27 Mark Struberg <strub...@yahoo.de>

> Nicolas,
>
> I'm currently reviewing your github work. It basically looks good, but it
> should be applied to trunk (maven-2.x). The changes you did needs java5, but
> wagon-1.x is still java-1.4 only. Switching to java5 is one of the main
> difference between wagon-1.x and wagon-2.x
>
> The patch should pretty much apply without much changes.
>
> txs and LieGrue,
> strub
>
> --- On Sat, 8/27/11, nicolas de loof <nicolas.del...@gmail.com> wrote:
>
> > From: nicolas de loof <nicolas.del...@gmail.com>
> > Subject: Re: fix wagon http lightweight
> > To: "Maven Developers List" <dev@maven.apache.org>
> > Date: Saturday, August 27, 2011, 5:27 AM
> > I just can't get git svn to work and
> > push my changes to wagon 1.x branch
> > feel free to pick-up those changes if you like them
> >
> > 2011/8/24 nicolas de loof <nicolas.del...@gmail.com>
> >
> > > I'm testing a fix for WAGON-346<
> http://jira.codehaus.org/browse/WAGON-346> and
> > > WAGON-347 <http://jira.codehaus.org/browse/WAGON-347>
> > > Before I commit anything to svn I'd like your advice :
> > see
> > > https://github.com/ndeloof/maven-wagon/tree/wagon-1.x
> > >
> > > The idea to make LightWeightHttpWagon thread-safe
> > despite the
> > > java.net.Authenticator static singleton, is to have a
> > custom Authenticator
> > > shared component and callback methods to the wagon
> > instance, using a
> > > ThreadLocal to keep track of "current" wagon
> > >
> > > For WAGON-347 the preemptive authentication can be
> > configured either per
> > > repository using a "preemptiveAuthentication"
> > parameter, or system wide
> > > using
> > -Dmaven.wagon.http.preemptiveAuthentication=true
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Reply via email to