Hi,
I've just enabled access logging on a Jenkins 1.562 test installation,
using Winstone command line options. I wonder why this can work since
https://wiki.jenkins-ci.org/display/JENKINS/Jetty says Jenkins 1.535
and above bundles Jetty (rather than Winstone)
Looking at jenkins.war, there's
To: jenkinsci-users@googlegroups.com
Subject: Jetty or Winstone
Hi,
I've just enabled access logging on a Jenkins 1.562 test installation, using
Winstone command line options. I wonder why this can work since
https://wiki.jenkins-ci.org/display/JENKINS/Jetty says Jenkins 1.535 and above
Am 07.05.2014 09:37, schrieb James Nord (jnord):
To preserve backwards compatibility of command line arguments a shim
was written to look like Winstone that maps arguments onto Jetty
specifics.
Ah, OK.
Thanks for clarifying this.
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems
:* jenkinsci-users@googlegroups.com [mailto:
jenkinsci-users@googlegroups.com] *On Behalf Of *Dirk Heinrichs
*Sent:* 07 May 2014 08:08
*To:* jenkinsci-users@googlegroups.com
*Subject:* Jetty or Winstone
Hi,
I've just enabled access logging on a Jenkins 1.562 test installation,
using Winstone
On 07/05/2014 10:44, Arnaud Héritier wrote:
thus the winstone jar is useless ?
No. winstone.jar is the thing that wraps Jetty and provides the same
features as the old winstone based winstone.jar.
https://github.com/jenkinsci/winstone
Regards
Richard
On Wed, May 7, 2014 at 9:37 AM,
ok,
thx
On Wed, May 7, 2014 at 11:52 AM, Richard Mortimer ri...@oldelvet.org.ukwrote:
On 07/05/2014 10:44, Arnaud Héritier wrote:
thus the winstone jar is useless ?
No. winstone.jar is the thing that wraps Jetty and provides the same
features as the old winstone based winstone.jar.
