Tom, I think we have made a mistake of using
logback.version=1.1.7 instead of logback.version?=1.1.7 as the later allows for the property to be overridden in the command line or in another module. Note that for the current release, the simplest approach to take is to copy the logback-impl.mod from the jetty distribution into your $JETTY_BASE/modules and modify it as need be. If you are supplying the jars yourself, then you can remove the Files section as well. cheers On 21 April 2017 at 10:58, Tom Zeller <[email protected]> wrote: > Hi, > > In 9.4, is it possible to override logback.version from the command > line or via .ini or module files in jetty.base ? > > The only way I have found is to copy > jetty.home/modules/logback-impl.mod to jetty.base and change > logback.version there. It seems that properties specified in [ini] > declarations are not overridable. > > I ask because we supply a later version of logback in our product. > > And, as a follow up, I guess I am curious why Jetty pins a specific > version of logback. That wasn't the case in 9.3, AFAIK. Ideally > logback.version would be '*'. > > Thanks, > Tom > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users > -- Greg Wilkins <[email protected]> CTO http://webtide.com
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
