Emit "bytes" as part of Content-Range header per RFC2616.
Makes it work with Chrome and fixes JENKINS-13125.
supported setter injection in addition to the constructor injection
switched to JSR-305
completed setter injection by adding a test case
require a setter annotation
Updated the dependency on Guava (r06 -> 15.0)
Use LoadingCache.getUnchecked() to avoid catching the ExecutionException
Prevent automatic exporting of taglibs into ancestor scopes

Stephen Connolly found out that various <d:taglib name="local">
that we see inside Jenkins have actually been overwriting each
other.

This is because Jelly automatically propagates namespace to taglib
binding to ancestor contexts, unless set explicitly not to.

In our usage in Jenkins (and by extrapolation elsewhere in Stapler),
this is never a desirable behaviour. We'd rather want namespaces to
act like they are lexically scoped.

This change configures new Jelly contexts correctly when it's created
via <st:include> or when used through a tag file invocation.

Grepping on Jenkins source tree confirms that these are the only
usage in question to fix the problems.
[maven-release-plugin] prepare release stapler-parent-1.219
[maven-release-plugin] prepare for next development iteration
[JENKINS-19473] Pick up fixed version of jzlib.
added field injection
added @PostConstruct support
on 2nd thought, allowing multiple methods
documenting this support
corrected typo
added another layer of BindInterceptors at the global level
doc improvement
adding another interception mechanism to intercept instantiation
adding test for BindInterceptors