Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to Jhipster 7.9.3 #143

Open
rseedorff opened this issue Aug 31, 2022 · 3 comments · May be fixed by #144
Open

Upgrade to Jhipster 7.9.3 #143

rseedorff opened this issue Aug 31, 2022 · 3 comments · May be fixed by #144
Assignees
Labels
dependencies Pull requests that update a dependency file
Milestone

Comments

@rseedorff
Copy link
Contributor

rseedorff commented Aug 31, 2022

There is a new JHipster release v7.9.2 but it includes a lot of changes. We need to upgrade due to some outdated dependencies also.

@rseedorff rseedorff self-assigned this Aug 31, 2022
@rseedorff rseedorff added the dependencies Pull requests that update a dependency file label Aug 31, 2022
@rseedorff rseedorff added this to the v2.1.0 milestone Aug 31, 2022
@rseedorff rseedorff linked a pull request Sep 1, 2022 that will close this issue
1 task
@Weltraumschaf
Copy link
Member

Jhipster Issue to track blocker progress

@rseedorff
Copy link
Contributor Author

There is a new patch release:
https://www.jhipster.tech/2022/09/02/jhipster-release-7.9.3.html

@Weltraumschaf Weltraumschaf changed the title Upgrade to Jhipster 7.9.2 Upgrade to Jhipster 7.9.3 Oct 18, 2023
@Weltraumschaf
Copy link
Member

We identified the Problem which hinders us from upgrading: In the frontend code we rely on some model properties which were never meant to be genenerated. In the Java code they were never generated in the DTOs. In 1:n releations the other side is only accessible in the "owner" side. This is specified by JPA and is so since ever. It was a bug in the JHipser generators that these properties were generated in the TS code. This was fixed in v7.9.2 of JHipster. Sadly we use these properties in lot of places in our custom code.

We need to investigate all the places to see how much effort it is to fix all of them, before we can upgrade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants