v8 stable release. #23449

mshima · 2023-09-08T14:52:10Z

deepu105 · 2023-09-16T05:02:44Z

I don't think we have to wait for all blueprints to migrate as they can migrate at their own pace

nicolas63 · 2023-09-17T07:42:35Z

I have create the issue on the jhipter-dotnet blueprint but i need your help to migrate

mshima · 2023-09-23T11:28:36Z

I have create the issue on the jhipter-dotnet blueprint but i need your help to migrate

I’ve started the migration.

mraible · 2023-09-27T05:01:20Z

@mshima I appreciate all the work you're doing to make JHipster 8.0 happen. Please let me know if there's anything I can do to help!

mshima · 2023-09-29T16:17:41Z

@mraible some help updating heroku generator would be great. We should target heroku for 8.1.

With micronaut (java) and dotnetcore (2 client generators and a server) been updated.
I would say we should go ahead and release a RC as soon as possible and final a week later.

I will take a look at ci-cd generator and nodejs and ionic blueprints this weekend.

I hope to have a simultaneous release for every migrated blueprint.

deepu105 · 2023-10-04T23:04:59Z

I can do and RC release this weekend. Let me know if I should wait for any ticket to be merged

…

On Fri, 29 Sept 2023, 6:17 pm Marcelo Shima, ***@***.***> wrote: @mraible <https://github.com/mraible> some help updating heroku generator would be great. We should target heroku for 8.1. With micronaut (java) and dotnetcore (2 client generators and a server) been updated. I would say we should go ahead and release a RC as soon as possible and final a week later. I will take a look at ci-cd generator and nodejs and ionic blueprints this weekend. I hope to have a simultaneous release for every migrated blueprint. — Reply to this email directly, view it on GitHub <#23449 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIOKF7LL3VWT7CSEX3EWQ3X43YDBANCNFSM6AAAAAA4QQDERM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

mshima · 2023-10-13T11:21:15Z

@deepu105 any news about a new release?

deepu105 · 2023-10-13T21:31:12Z

I waiting for confirmation. I can do the RC release tomorrow.

…

On Fri, 13 Oct 2023, 1:21 pm Marcelo Shima, ***@***.***> wrote: @deepu105 <https://github.com/deepu105> any news about a new release? — Reply to this email directly, view it on GitHub <#23449 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIOKFZJTYNITOQLQWCP5LDX7EP3NANCNFSM6AAAAAA4QQDERM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

mraible · 2023-10-30T03:30:02Z

I might've fixed #23883. If it works, can you create a release this week, @deepu105?

mshima · 2023-10-30T17:23:52Z

@mshima I tried creating a new micro frontends architecture using:

jhipster jdl reactive-mf.jdl --monorepository --workspaces

It gives me a bunch of warnings. Do I need to update the reactive-mf.jdl file to add a custom id?

WARNING! Microservice entities should have a custom id to make sure gateway and microservice types won't conflict
WARNING! Microservice entities should have a custom id to make sure gateway and microservice types won't conflict
WARNING! Microservice entities should have a custom id to make sure gateway and microservice types won't conflict
WARNING! Microservice entities should have a custom id to make sure gateway and microservice types won't conflict

@mraible fixed in #24046.

mraible · 2023-10-31T02:22:34Z

👀 Our quality gate is looking good!

@mshima @DanielFran Do we need anything else before releasing 8.0?

DanielFran · 2023-10-31T12:17:03Z

@mraible I believe everything is done.

We still have this PR to remove AngularJS locale configuration but we do not have anything to replace that could manage i18n. But I do not think this is blocking the release.

And I realised that today Neo4J is broken: https://github.com/hipster-labs/jhipster-daily-builds/actions/runs/6702088203

DanielFran · 2023-10-31T13:33:37Z

@mshima Is this #24028 blocking the release?

mshima · 2023-10-31T16:06:40Z

@mshima Is this #24028 blocking the release?

It's a quite annoying bug, not sure how much the user is affected.
Are you planning to cut the release?

mshima · 2023-10-31T16:08:00Z

@mshima Is this #24028 blocking the release?

This is actually jhipster v7 behavior, since we used to delegate to the local generator-jhipster.

DanielFran · 2023-10-31T17:36:22Z

@mshima Is this #24028 blocking the release?

It's a quite annoying bug, not sure how much the user is affected. Are you planning to cut the release?

I believe it was supposed to create the final version now, not a new RC version

mshima · 2023-10-31T18:22:10Z

@mshima Is this #24028 blocking the release?

It's a quite annoying bug, not sure how much the user is affected. Are you planning to cut the release?

I believe it was supposed to create the final version now, not a new RC version

Yes, there are huge changes to the core since the RC, but I think it's ok to go final.
I want to know if you are planning to release in the middle of this week.

mraible · 2023-10-31T18:30:49Z

@mshima What's your preference? As the primary contributor to 8.0, we're happy to follow your advice.

@deepu105 Can you do a release today or tomorrow if everyone approves? It might be fun to release on Halloween! 👻🎃

mshima · 2023-11-01T02:01:06Z

One last PR #24067.

MarkingYang · 2023-11-01T02:02:18Z

您好，我最近学业繁忙，无法亲自回复您的邮件。晚间查看后，会尽快给您回复。

mraible · 2023-11-01T03:56:03Z

@mshima I'm testing this blog post and when I run jhipster jdl microservices.jdl, it still has warnings:

WARNING! Microservice entities should have a custom id to make sure gateway and microservice types won't conflict
WARNING! Microservice entities should have a custom id to make sure gateway and microservice types won't conflict
WARNING! Microservice entities should have a custom id to make sure gateway and microservice types won't conflict
WARNING! Microservice entities should have a custom id to make sure gateway and microservice types won't conflict
WARNING! Microservice entities should have a custom id to make sure gateway and microservice types won't conflict

Here's the JDL:

application {
  config {
    baseName gateway
    packageName com.okta.developer.gateway
    applicationType gateway
    authenticationType oauth2
    buildTool gradle
    clientFramework vue
    prodDatabaseType postgresql
    serviceDiscoveryType consul
    testFrameworks [cypress]
  }
  entities Blog, Post, Tag, Product
}

application {
  config {
    baseName blog
    packageName com.okta.developer.blog
    applicationType microservice
    authenticationType oauth2
    buildTool gradle
    databaseType neo4j
    enableHibernateCache false
    serverPort 8081
    serviceDiscoveryType consul
  }
  entities Blog, Post, Tag
}

application {
  config {
    baseName store
    packageName com.okta.developer.store
    applicationType microservice
    authenticationType oauth2
    buildTool gradle
    databaseType mongodb
    enableHibernateCache false
    serverPort 8082
    serviceDiscoveryType consul
  }
  entities Product
}

entity Blog {
  name String required minlength(3)
  handle String required minlength(2)
}

entity Post {
  title String required
  content TextBlob required
  date Instant required
}

entity Tag {
  name String required minlength(2)
}

entity Product {
  title String required
  price BigDecimal required min(0)
  image ImageBlob
}

relationship ManyToOne {
  Blog{user(login)} to User with builtInEntity
  Post{blog(name)} to Blog
}

relationship ManyToMany {
  Post{tag(name)} to Tag{post}
}

paginate Post, Tag with infinite-scroll
paginate Product with pagination

microservice Product with store
microservice Blog, Post, Tag with blog

deployment {
  deploymentType docker-compose
  appsFolders [gateway, blog, store]
  dockerRepositoryName "mraible"
}

The rest of the tutorial works, there's just this these warnings at the beginning.

mshima · 2023-11-01T10:03:39Z

@mraible some context of this warning is at #23850

At the PR we started relying on the frontend type to do some conversions and failed due to id different types related to different databases (gateway uses postgres with Long ids, microservice uses cassandra with UUID ids).

We used to carry on databaseType at the entity level, but this is quite hackish and hard to maintain, and we are decoupling jdl from business.
As alternative, we are advising the user to specify the entity's id type which looks much more reliable and cleaner than carrying databaseType around at entity level.

deepu105 · 2023-11-01T13:24:01Z

I'll do the release sometime this week

…

On Wed, 1 Nov 2023, 11:03 am Marcelo Shima, ***@***.***> wrote: @mraible <https://github.com/mraible> some context of this warning is at #23850 <#23850> At the PR we started relying on the frontend type to do some conversions and failed due to id different types related to different databases (gateway uses postgres with Long ids, microservice uses cassandra with UUID ids). We used to carry on databaseType at the entity level, but this is quite hackish and hard to maintain, and we are decoupling jdl from business. As alternative, we are advising the user to specify the entity's id type which looks much more reliable and cleaner than carrying databaseType around at entity level. — Reply to this email directly, view it on GitHub <#23449 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIOKF4D4R6EJSYNJ4C6GU3YCINANAVCNFSM6AAAAAA4QQDEROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBYG4YDAOJTGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

mraible · 2023-11-01T14:08:28Z

As alternative, we are advising the user to specify the entity's id type which looks much more reliable and cleaner than carrying databaseType around at entity level.

How do I change my JDL to get rid of this warning?

mshima · 2023-11-01T14:27:06Z

As alternative, we are advising the user to specify the entity's id type which looks much more reliable and cleaner than carrying databaseType around at entity level.

How do I change my JDL to get rid of this warning?

Neo4J and MongoDB default primary keys are String and there is no entity served in Gateway.
Add id String field to every entity.

mraible · 2023-11-01T16:48:16Z

I can confirm that adding id String to the JDL makes the warning go away. Here's the commit with the update. Is required necessary for primary keys?

mshima · 2023-11-01T17:17:59Z

I can confirm that adding id String to the JDL makes the warning go away. Here's the commit with the update. Is required necessary for primary keys?

No, the id should imply required.
Maybe you want to add the Id annotation @Id id String I think is prettier.

mraible · 2023-11-01T17:34:09Z

OK, updated in oktadev/okta-blog@9f4f171.

In the generated Java classes, I noticed the biggest difference is removing required results in @NotNull being removed:

-    @NotNull
     @Id
     private String id;

mshima · 2024-05-20T19:07:55Z

@DanielFran bounty claimed https://opencollective.com/generator-jhipster/expenses/203358.

DanielFran · 2024-05-21T08:28:28Z

@mshima approved

mshima added area: enhancement 🔧 theme: blueprint 🐾 v8 labels Sep 8, 2023

ghost mentioned this issue Sep 13, 2023

Migrate to JHipster v8 jhipster/generator-jhipster-nodejs#300

Closed

8 tasks

mshima mentioned this issue Sep 15, 2023

Follow option imports at blueprints. #23523

Merged

6 tasks

nicolas63 mentioned this issue Sep 17, 2023

Migrate to JHipster v8 jhipster/jhipster-dotnetcore#1340

Closed

mraible mentioned this issue Sep 21, 2023

Timeline for jHipster v8 / Spring 6 Upgrade #20748

Closed

mraible added $$ bug-bounty $$ https://www.jhipster.tech/bug-bounties/ $500 https://www.jhipster.tech/bug-bounties/ labels Sep 21, 2023

This was referenced Sep 22, 2023

Improve blueprint support. #23591

Merged

Blueprint support improvements. #23598

Merged

Split README fragments #23599

Merged

mshima mentioned this issue Sep 25, 2023

Adjusts for dotnetcore blueprint #23616

Merged

6 tasks

This was referenced Sep 28, 2023

Misc improvements #23668

Merged

improve docker generator for blueprints #23676

Merged

Client rework. #23680

Merged

This was referenced Oct 2, 2023

Rework ci-cd for v8 #23718

Merged

move entities and enums to the java generator #23732

Merged

rename javadoc to documentation #23742

Merged

This was referenced Oct 6, 2023

Adjusts for improved blueprint support. #23762

Merged

compose bootstrap* with blueprints #23802

Merged

Rework entity generator #23804

Merged

mshima mentioned this issue Oct 30, 2023

remove warning for microfrontends #24046

Merged

6 tasks

mshima mentioned this issue Oct 30, 2023

add java samples class for entities and increase coverage #24051

Merged

6 tasks

mshima mentioned this issue Nov 1, 2023

Adjusts for v8 #24067

Merged

6 tasks

mshima mentioned this issue Nov 1, 2023

start replacing ownerSide property #24073

Merged

6 tasks

DanielFran closed this as completed Nov 2, 2023

deepu105 modified the milestones: 8.1.0, 8.0.0 Dec 11, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

v8 stable release. #23449

v8 stable release. #23449

mshima commented Sep 8, 2023 •

edited by mraible

Loading

deepu105 commented Sep 16, 2023

nicolas63 commented Sep 17, 2023

mshima commented Sep 23, 2023

mraible commented Sep 27, 2023

mshima commented Sep 29, 2023

deepu105 commented Oct 4, 2023 via email

mshima commented Oct 13, 2023

deepu105 commented Oct 13, 2023 via email

mraible commented Oct 30, 2023

mshima commented Oct 30, 2023

mraible commented Oct 31, 2023 •

edited

Loading

DanielFran commented Oct 31, 2023

DanielFran commented Oct 31, 2023 •

edited

Loading

mshima commented Oct 31, 2023 •

edited

Loading

mshima commented Oct 31, 2023

DanielFran commented Oct 31, 2023

mshima commented Oct 31, 2023

mraible commented Oct 31, 2023

mshima commented Nov 1, 2023

MarkingYang commented Nov 1, 2023 via email

mraible commented Nov 1, 2023 •

edited

Loading

mshima commented Nov 1, 2023

deepu105 commented Nov 1, 2023 via email

mraible commented Nov 1, 2023

mshima commented Nov 1, 2023

mraible commented Nov 1, 2023

mshima commented Nov 1, 2023 •

edited

Loading

mraible commented Nov 1, 2023

mshima commented May 20, 2024

DanielFran commented May 21, 2024

v8 stable release. #23449

v8 stable release. #23449

Comments

mshima commented Sep 8, 2023 • edited by mraible Loading

Overview of the feature request

Motivation for or Use Case

Related issues or PR

deepu105 commented Sep 16, 2023

nicolas63 commented Sep 17, 2023

mshima commented Sep 23, 2023

mraible commented Sep 27, 2023

mshima commented Sep 29, 2023

deepu105 commented Oct 4, 2023 via email

mshima commented Oct 13, 2023

deepu105 commented Oct 13, 2023 via email

mraible commented Oct 30, 2023

mshima commented Oct 30, 2023

mraible commented Oct 31, 2023 • edited Loading

DanielFran commented Oct 31, 2023

DanielFran commented Oct 31, 2023 • edited Loading

mshima commented Oct 31, 2023 • edited Loading

mshima commented Oct 31, 2023

DanielFran commented Oct 31, 2023

mshima commented Oct 31, 2023

mraible commented Oct 31, 2023

mshima commented Nov 1, 2023

MarkingYang commented Nov 1, 2023 via email

mraible commented Nov 1, 2023 • edited Loading

mshima commented Nov 1, 2023

deepu105 commented Nov 1, 2023 via email

mraible commented Nov 1, 2023

mshima commented Nov 1, 2023

mraible commented Nov 1, 2023

mshima commented Nov 1, 2023 • edited Loading

mraible commented Nov 1, 2023

mshima commented May 20, 2024

DanielFran commented May 21, 2024

mshima commented Sep 8, 2023 •

edited by mraible

Loading

mraible commented Oct 31, 2023 •

edited

Loading

DanielFran commented Oct 31, 2023 •

edited

Loading

mshima commented Oct 31, 2023 •

edited

Loading

mraible commented Nov 1, 2023 •

edited

Loading

mshima commented Nov 1, 2023 •

edited

Loading