Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Debugging a dry-run issue

This is the change from Issue
With the change from pull-request

What specific OS are you using? (we tested that change on Linux + Windows 10 + OSX without issue)
And how are you using the --dry-run?

We will likely need to make adjustments to this, but we need more feedback first.
The new Issue at could be a place to coordinate this.

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Wed, Apr 19, 2023 at 12:36 PM Cantor, Scott <cantor.2@xxxxxxx> wrote:
I think this commit between 10.0.14 and 10.0.15 is breaking my init script, which I know is quite non-optimal, but for debugging purposes...could I ask what the purpose of [1] is and what its functional impact is supposed to be?

What I think is happening is that it's single-quoting all my ini-sourced properties. Simple excerpt from --dry-run:



It's clear from my results that Jetty does not see the latter at all, it's ignoring all my properties and using its defaults, but I don't know if I'm overlooking anything. Thought I'd start with "what's the intended change?".

I have historically had to do some sed magic on --dry-run to keep things working and I can probably do the same since I don't think my working command lines ever had any single quotes, but I'm still poking.

-- Scott


jetty-users mailing list
To unsubscribe from this list, visit

Back to the top