Hipster stack for Java developers. Spring Boot + Angular in one handy generator.
rm package-lock.json
rm -rf node_modules
npm i
[INFO] WARNING in ./src/main/webapp/app/shared/question/question.component.ts 60:87-96
[INFO] "export 'IQuestion' was not found in 'app/shared/model/question.model'@ruddell i would like to give feedback on the upgrade, not sure how to do it, i guess you are close to the commiters :)
with this upgrade the path of fake data changed, which is a minor thing. but what happens is that the liquibase files need a change.
the way liquibase works is that it keeps track of files it has run and hash them. so changing old files is not possible.
so now this minor change gets into a problem. if i want to recreate my local db i need to change this url but if I do my production base will not work and liquibase will complain that there has been made changes.
type: com.zaxxer.hikari.HikariDataSource
url: jdbc:mariadb://localhost:3306/deeldocent?useLegacyDatetimeCode=false&serverTimezone=UTC
username: dedo
Well we tried your first option, but got ```ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: Invocation of init method failed; nested exception is org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.cache.spi.RegionFactory]
2019-09-05 14:58:07.610 WARN 10406 --- [arch-Executor-1] com.zaxxer.hikari.pool.ProxyConnection : HikariPool-1 - Connection com.mysql.jdbc.JDBC4Connection@11bc7b20 marked as broken because of SQLSTATE(08S01), ErrorCode(0)
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
The last packet successfully received from the server was 8 milliseconds ago. The last packet sent successfully to the server was 7 milliseconds ago.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)```
short questions in regards to https://www.jhipster.tech/using-uaa/
how are the access tokens checked when a resource server is called? Does it just check the signature and expiration or is there an additional check against a blacklist e.g. managed with redis for example?
Hello! I get the infamous "The JDL object and the database type are both mandatory." error while importing JDL into a project generated with Kotlin and Vue.js blueprints. I did a console.log in entity_parser.js in the place where the error occurs and other information is present, but DB type is indeed missing:
INFO! The JDL is being parsed.
{ jdlObject:
JDLObject {
applications: {},
deployments: {},
entities:
{ Bin: [JDLEntity], BinSession: [JDLEntity], User: [JDLEntity] },
enums: JDLEnums { enums: [Map] },
relationships: JDLRelationships { relationships: [Object] },
options: JDLOptions { options: [Object], optionSize: 3 } },
applicationType: 'monolith',
databaseType: undefined }
Error: The JDL object and the database type are both mandatory.Before running the import, I generated the application and generation seemed to succeed, the application runs without errors and I can log in.
keycloak.USER_ENTITY.ID be the same as my jhipsterdb.jhi_user.id? When I create a new user in the app (register them), it uses Keycloak to create the user and I can see it in the keycloak.USER_ENTITY table. Jhipster will sync that user up so that new user gets added to jhipsterdb.jhi_user, however, I do see users in jhipsterdb.jhi_user that have different GUID ID's than that is in keycloak.USER_ENTITY. Should I try to clean these up and keep them the same? I am asking because I am adding a user_extra table and I was thinking I needed a foreign key to jhi_user and that is when I noticed these IDs are not the same. Is this a good practice to keep them the same or does it not matter? Thanks.
Non-resolvable import POM: Failure to find io.github.jhipster:jhipster-dependencies:pom:3.0.5-SNAPSHOT in http://oss.sonatype.org/content/repositories/snapshots was cached in the local repository
@/all Full disclosure of the security vulnerability in JHipster. This enables account takeover of any of your users arbitrarily.
https://github.com/jhipster/generator-jhipster/issues/10401#issuecomment-531404568
