Update blueprints to generator-jhipster v8.9.0

[mshima]

Overview of the feature request

• generator-jhipster-native v2.6.0
• generator-jhipster-migrate v1.7.0
• generator-jhipster-entity-audit v5.9.0
• generator-jhipster-ionic v8.5.0
• generator-jhipster-react-native v5.3.0
• generator-jhipster-micronaut v3.7.0
• generator-jhipster-nodejs update generator-jhipster to 8.9.0 generator-jhipster-nodejs#702
• generator-jhipster-quarkus v3.5.0
• generator-jhipster-jooq v3.4.0
• jhipster-dotnetcore v4.4.1
• jhipster-kotlin

Motivation for or Use Case

Related issues or PR

• Checking this box is mandatory (this is just to show you read everything)

[mshima]

@mraible I don't have permission to release others blueprints.
The missing blueprint is kotlin.

[mraible]

I can work on Ionic, React Native, Micronaut, and Quarkus.

[mraible]

New versions have now been released for Ionic, React Native, Micronaut, and Quarkus.

[nicolas63]

I can do it for dotnet

[mraible]

@mshima Should we announce the release now or wait for Node and .NET?

[mshima]

I think we should announce.
It’s been 8 months since last NodeJS blueprint release

[nicolas63]

done for dotnet : https://github.com/jhipster/jhipster-dotnetcore/releases/tag/v4.4.1

[mshima]

@DanielFran @mraible can you give me rights to release nodejs blueprint?
What about kotlin? We may release beta versions since it still using Spring Boot 2.

[mraible]

@mshima I made you an admin on both projects.

[mshima]

@mshima I made you an admin on both projects.

Thanks I need npm access to them too.

[mraible]

@mshima I see you as a member in the jhipster org on npmjs.com. Is that enough to publish? Unfortunately, jhipster-kotlin is not under the jhipster org, so I can't control those permissions.

[mshima]

@mshima I see you as a member in the jhipster org on npmjs.com. Is that enough to publish? Unfortunately, jhipster-kotlin is not under the jhipster org, so I can't control those permissions.

No.
Can you add release permission to blueprint team?
Or create a new team blueprints-maintainers.

[mraible]

@jdubois Can you help with this? I don't want to mess anything up.

[jdubois]

Unfortunately, I don't see a JHipster org on NPM. I remember we didn't create one because it required us to pay a subscription, and at that time we had no sponsorship money.
So I believe each blueprint is owned by the person who created them. For Kotlin is seems to be @sendilkumarn -> https://www.npmjs.com/package/generator-jhipster-kotlin

[mraible]

@jdubois I see a JHipster org at https://www.npmjs.com/settings/jhipster/packages. There are 20 packages, 15 members, and 11 teams. The blueprint team has 5 members, with three packages:

• generator-jhipster-module
• generator-jhipster-blueprint
• generator-jhipster-entity-audit

There are a few teams for specific blueprints:

• nodejs-blueprint
• dotnet-core
• jooq
• svelte
• quarkus

More consistency would be nice.

[mshima]

The packages generator-jhipster-blueprint and generator-jhipster-module should be deprecated.

[jdubois]

Oh sorry @mraible ! The NPM UI is really bad, I missed the JHipster org... I don't remember the limitation we had, anyway we don't pay for subscription.
As generator-jhipster-kotlin isn't part of the org, I can't do anything -> @sendilkumarn would you like to transfer it the org? If I remember correctly, this first needs to go through me (as I'm an org owner), and then I'll transfer it from my own account to the org.