Ralf D. Müller

@jmini , yes this is related. the approach described in the tutorial is the old one, but works. the ng-branch needs to clone the reveal-js stuff to work. It is...

[x] fix for local bash [ ] fix for docker image [x] fix for powershell / cmd

thanx for reporting this issue. The code for `publishToConfluence` hasn't been touched in a while and I don't recognize this exception from Jira. It seems that the calling system tries...

hm. I use the cloud instance of confluence and it is hard to tell which version is behind it. you stacktrace mentions problems with cookies and I don't know where...

thanx for all this analysis output. let's see what we've got: - the response seems to be a 200 or at least no error status (have we validated the 200?)...

@bodewig : the error message comes from *which* client? I doubt that it is the docToolchain client (there is no set-cookie header). So it would be a system (CROWD SSO?)...

thanx for the input! so, basically, CROWD sets a cookie which docToolchain rejects because of a too strict implementation. to solve this, we have to reconfigure our client or replace...

closed by mistake

see also https://github.com/confluence-publisher/confluence-publisher/pull/154/files and https://github.com/confluence-publisher/confluence-publisher/issues/153 I think this is the same problem

thanx for raising this issue. The publishToConfluence tasks uses the output of the generateHTML task. So I guess the images are already broken there and this might be easier to...