Timothy Stone

Seeing the same problem. Fresh install using a monolith with Jhipster 7.9.2.

> needs to be rebased on `master` since it is pointing at an EOL branch. Is this the only thing holding this PR back @mbien ?

@mraible @mshima I think this page needs more work. It's dated as is even with my updates (which may only raise awareness). I could not get `jhipster update` to complete...

Regarding my public gist for the Git graph. It's more stable than the JSFiddle that is currently provided, read: it doesn't work. @atomfrede I think it's probably prudent to fork...

> @timothystone Can you please fix conflicts if this page still needs to be updated? I tried using the [current page](https://www.jhipster.tech/upgrading-an-application/) to update my jhipster8-demo app last night and it...

> > hi @dacr thanks for the PR, if you could solve the conflicts and change the test in https://github.com/carlossg/docker-maven/blob/main/tests/tests.bats#L162-L165 I'll merge it for the next maven release > >...

> > > hi @dacr thanks for the PR, if you could solve the conflicts and change the test in https://github.com/carlossg/docker-maven/blob/main/tests/tests.bats#L162-L165 I'll merge it for the next maven release >...

Any updates on this? Seems like a legitimate need for expected compatibility of core Maven plugins. Maybe `jgit` is a workaround, but it can be troublesome in numerous edge cases....

> Would you consider a PR if I were to add `ssh` to all the Dockerfiles and resolve any tests? OSS invites PRs @seanmmills. I suggest forking and opening the...