Wagon are noted "per-lookup". Have a look at DefaultWagonManager in core, this one always do a container.lookup to get a new fresh wagon instance. So normally plugins using WagonManager must not have any issues (except reusing the same wagon instance)
2013/1/9 Kristian Rosenvold <[email protected]>: > To illustrate the point I'm trying to make: > > org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon line 240: > > protected ClientConnectionManager clientConnectionManager = new > SingleClientConnManager(); > > Now read the docs for SingleClientConnManager (annotated as @ThreadSafe!): > > "Even though this class is thread-safe it ought to be used by one > execution thread only" > > This "ought to" means that it's probably unwise to handoff such an > instance to a different thread down the line, which we do. So it does > not support serial thread confinement. It makes me wonder about the > @ThreadSafe annotation.... > > Kristian > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
