I had this exception in a onetoone relation defined in jhipster:
org.hibernate.AnnotationException: Unknown mappedBy in:
com.plan.vima.domain.Warehouse.orderItem, referenced property unknown:
com.plan.vima.domain.OrdemItem.ordemItem
this was the relationship that I added and that caused my issue:
relationship OneToOne {
OrdemItem to Warehouse {orderItem}
}
Please note that I got this exception running the project as it was jenerated by jhipster after i imported the enetities and the relations - i did notn wrote a line of code.
this is my complete Jhipster project info:
C:\myjh\relwithusers6>jhipster info
Using JHipster version installed locally in current project's node_modules
Executing jhipster:info
Options:
Welcome to the JHipster Information Sub-Generator
##### **JHipster Version(s)**
relwithusers-6#0.0.0 C:\myjh\relwithusers6
`-- generator-jhipster#5.0.1
##### **JHipster configuration, a `.yo-rc.json` file generated in the root folde
r**
<details>
<summary>.yo-rc.json file</summary>
<pre>
{
"generator-jhipster": {
"promptValues": {
"packageName": "com.plan.vima"
},
"jhipsterVersion": "5.0.1",
"applicationType": "monolith",
"baseName": "relwithusers6",
"packageName": "com.plan.vima",
"packageFolder": "com/plan/vima",
"serverPort": "8080",
"authenticationType": "jwt",
"cacheProvider": "ehcache",
"enableHibernateCache": true,
"websocket": false,
"databaseType": "sql",
"devDatabaseType": "h2Disk",
"prodDatabaseType": "postgresql",
"searchEngine": false,
"messageBroker": false,
"serviceDiscoveryType": "eureka",
"buildTool": "maven",
"enableSwaggerCodegen": false,
"jwtSecretKey": "replaced-by-jhipster-info",
"clientFramework": "angularX",
"useSass": true,
"clientPackageManager": "npm",
"testFrameworks": [],
"jhiPrefix": "jhi",
"enableTranslation": false
}
}
</pre>
</details>
##### **JDL for the Entity configuration(s) `entityName.json` files generated in
the `.jhipster` directory**
<details>
<summary>JDL entity definitions</summary>
<pre>
entity Ordem (ordem) {
ordemNumber String,
dateOpen Instant,
dateClose Instant,
totalAmount Double,
orderstatus Orderstatus
}
entity OrdemItem (ordem_item) {
quantityRequired Integer,
quantityNegotiated Integer,
quantityShipped Integer,
orderstatus Orderstatus
}
entity Warehouse (warehouse) {
unitPrice Double,
quantityRemaining Integer
}
entity Product (product) {
productName String,
unitPrice Double,
isDiscontinued Boolean
}
enum Orderstatus {
REQUIRED,
ABORTED,
SHIPPED,
PARTIALLTYSHIPPED,
NOTSHIPPED,
NOPROD_NOTSHIPPED
}
relationship OneToOne {
OrdemItem{warehouse} to Warehouse
}
relationship OneToMany {
Ordem{orderItem} to OrdemItem{ordem},
Product{orderItem} to OrdemItem{product}
}
relationship ManyToOne {
Ordem{user(login)} to User,
Product{user(login)} to User
}
paginate Ordem, OrdemItem, Warehouse, Product with pagination
</pre>
</details>
##### **Environment and Tools**
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)
git version 2.20.1.windows.1
node: v10.15.1
npm: 6.7.0
yeoman: 2.0.5
Congratulations, JHipster execution is complete!
I think it should be like this:
relationship OneToOne {
OrdemItem(warehouse) to Warehouse {orderItem}
}
Because the owner of the relationship is OrdemItem.
See more example here
Related
I'm doing a course where we are using express-node postgres and react (with typescript) and typeORM. Everything has worked well so far, but I'm facing an issue with typeORM and I don't know what is going and why is this error happening
The Big Problem : So, the problem is that, I was doing the auth, and at some point we changed users schema in the DB so we had to make a migration, but, before migration, we did npm run typeorm schema:drop ,but when I tried, this happened with migration
This is the first command I used
npm run typeorm migration:generate -- --n create-users-table
This was the error
> new-typeorm-project#0.0.1 typeorm C:\Users\diego cifuentes\Desktop\Studying Backend\redit> ts-node ./node_modules/typeorm/cli.js "migration:generate" "create-users-table"
bin.js migration:generate
Generates a new migration file with sql needs to be executed to update
schema.
Opciones:
-h, --help Muestra ayuda [booleano] -c, --connection Name of the connection on which run a query.
[defecto: "default"] -n, --name Name of the migration class.
[cadena de caracteres] [requerido] -d, --dir Directory where migration should be created.
-p, --pretty Pretty-print generated SQL
[booleano] [defecto: false] -f, --config Name of the file with connection configuration.
[defecto: "ormconfig"] -o, --outputJs Generate a migration file on Javascript instead of
Typescript [booleano] [defecto: false] --dr, --dryrun Prints out the contents of the migration instead of
writing it to a file [booleano] [defecto: false] --ch, --check Verifies that the current database is up to date and that no migrations are needed. Otherwise exits with
code 1. [booleano] [defecto: false] -v, --version Muestra número de versión [booleano]
Falta argumento requerido: n
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! new-typeorm-project#0.0.1 typeorm: `ts-node ./node_modules/typeorm/cli.js "migration:generate" "create-users-table"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the new-typeorm-project#0.0.1 typeorm script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\diego cifuentes\AppData\Roaming\npm-cache\_logs\2021-05-11T15_29_02_081Z-debug.log
After hours trying to search for solution everywhere, I change the last command to this one
npx typeorm migration:generate -- --n create-users-table
And the error was different this time, looks like this
No changes in database schema were found - cannot generate a migration. To create a new empty migration use "typeorm migration:create" command
So, I said, ok, I'm getting closer to fixing this, but... After hours ( again ) looking for a new answer, I couldn't find anything, so, I'm getting to a point where I need to write this post in order to fix my problem. So now, let me show you my ormconfig, my package.json and the entity I want to migrate in my postgres DB.
package.json (the script typeorm is at the end)
{
"name": "new-typeorm-project",
"version": "0.0.1",
"description": "Awesome project developed with TypeORM.",
"devDependencies": {
"#types/bcrypt": "^5.0.0",
"#types/cookie": "^0.4.0",
"#types/cookie-parser": "^1.4.2",
"#types/express": "^4.17.11",
"#types/jsonwebtoken": "^8.5.1",
"#types/morgan": "^1.9.2",
"#types/node": "^15.0.2",
"morgan": "^1.10.0",
"nodemon": "^2.0.7",
"ts-node": "^9.1.1",
"typescript": "^4.2.4"
},
"dependencies": {
"bcrypt": "^5.0.1",
"class-transformer": "^0.4.0",
"class-validator": "^0.13.1",
"cookie": "^0.4.1",
"cookie-parser": "^1.4.5",
"dotenv": "^9.0.1",
"express": "^4.17.1",
"jsonwebtoken": "^8.5.1",
"pg": "^8.4.0",
"reflect-metadata": "^0.1.10",
"typeorm": "0.2.32"
},
"scripts": {
"start": "ts-node src/server.ts",
"dev": "nodemon --exec ts-node src/server.ts",
"typeorm": "ts-node ./node_modules/typeorm/cli.js"
}
}
ormconfing.json Quick note : I changed entities, migrations and subscribers to .js, because with .ts was always giving me error.
{
"type": "postgres",
"host": "localhost",
"port": 5432,
"username": "**",
"password": "**",
"database": "**",
"synchronize": true,
"logging": true,
"entities": ["src/entities/**/*.js"],
"migrations": ["src/migrations/**/*.js"],
"subscribers": ["src/subscribers/**/*.js"],
"cli": {
"entitiesDir": "src/entities",
"migrationsDir": "src/migrations",
"subscribersDir": "src/subscribers"
}
}
And last thing I want to show you, even though it might not be that important, this is the users schema
import {
Entity as TOEntity,
Column,
Index,
BeforeInsert,
OneToMany
} from "typeorm";
import bcrypt from "bcrypt";
import { IsEmail, Length } from "class-validator";
import { Exclude } from "class-transformer";
import Entity from "./Entity";
// import Post from "./Post";
#TOEntity("users")
export default class User extends Entity {
constructor(user: Partial<User>) {
super();
Object.assign(this, user);
}
#Index()
#IsEmail()
#Column({ unique: true })
email: string;
#Index()
#Length(3, 200)
#Column({ unique: true })
username: string;
#Exclude()
#Length(6, 200)
#Column()
password: string;
// #OneToMany(() => Post, post => post.user)
// posts: Post[];
#BeforeInsert()
async hashedPassword() {
this.password = await bcrypt.hash(this.password, 6);
}
}
End Goal: So, if you can help me with this, you will save my life. One last thing is that I tried to post my problems first in the Spanish website of stack overflow, but nobody could help me, so maybe here someone will, thanks for your time and take care!
Change your entities, migrations and subscribers into your dist directory.
e.g.:
entities: ["dist/entities/**/*{.js,.ts}"],
migrations: ["dist/migrations/**/*{.js,.ts}"],
subscribers: ["dist/subscribers/**/*{.js,.ts}"],
dist directory is the directory which gets created when you build the app. You can find your dist directory using tsconfig.json -> compilerOptions -> outDir.
Then build your app again using npm run build and try to generate the migrations.
For me the ormconfig.json's was like this,
"entities": [
"dist/entity/**/*.ts"
],
"migrations": [
"src/migration/**/*.ts"
],
"subscribers": [
"src/subscriber/**/*.ts"
],
Changing it to
"entities": [
"src/entity/**/*{.js,.ts}"
],
"migrations": [
"src/migration/**/*{.js,.ts}"
],
"subscribers": [
"src/subscriber/**/*{.js,.ts}"
],
generated the migration correctly.
And the package.json script is like this
"typeorm": "node --require ts-node/register ./node_modules/typeorm/cli.js"
And the command used is
npm run typeorm migration:generate -- -n FileAddTemporaryDeletedFields -p --dr --ch
I've seen this error, and if I'm not mistaken it's because I was trying to create a bank that had already been created.
This command below deletes all tables:
yarn typeorm query "DROP SCHEMA public CASCADE; CREATE SCHEMA public; GRANT USAGE ON SCHEMA public to PUBLIC; GRANT CREATE ON SCHEMA public to PUBLIC; COMMENT ON SCHEMA public IS 'standard public schema';"
then:
yarn typeorm --migration:generate -n migration_name -d path/to/your/migrations/
ormconfig.json is deprecated in latest version as i know.
but anyway I'm gonna share my solution when i used old version.
when generate, typeorm first reads ormconfig.json and login into rdbms.
and compares between 'the actual schema of db' and
'schema file as ormconfig.json[entities]'
so, if the file (writen at 'entities' in ormconfig.json) is in dist folder.
you have to edit that .js file.(not .ts file in src folder)
but, if the 'entities' file is in src folder as ormconfig.json,
check if 'autosave' feature of vscode is on.
if you 'npm run start:dev'
It could be the case that the actual schema of db has been already modified
before you edit entities file.
I have a simple JHipster JDL file that looks like below
entity Student {
name String,
age Integer
}
and I have this saved in a file called student.jh
Now I am trying to make use of the JHipster CLI and generate the entities needed for my dummy project. I noticed that by default JHipster ends up generating the following:
Entity classes
DTO classes
Repository classes
Service classes (I think this we can further customise by adding options as to whether we need service implementation as well)
Rest Controllers
Integration tests
Gatling tests (This I believe is configurable)
I was hoping to know if I could have JHipster skip generating the rest controllers because I would like to add custom rest controllers by hand. I know that I could merely have these controllers alone deleted (along with the Integration Tests that also get generated).
Is there any way in which this can be controlled? I have tried using all of the cli options for jhipster import-jdl but no luck yet.
here's the command I am using
jhipster import-jdl src/main/resources/student.jh
Here's the complete output
jhipster -d import-jdl src/main/resources/student.jh
INFO! Using JHipster version installed globally
DEBUG! Executing CLI only script
DEBUG! cmd: import-jdl from ./import-jdl
DEBUG! args: [object Undefined]
INFO! Executing import-jdl src/main/resources/student.jh
DEBUG! Options: debug: true, skip-install: false, interactive: false, json-only: false, ignore-application: false, ignore-deployments: false, skip-ui-grouping: false, skip-db-changelog: false, skip-sample-repository: false, skipInstall: false, jsonOnly: false, ignoreApplication: false, ignoreDeployments: false, skipUiGrouping: false, skipDbChangelog: false, skipSampleRepository: false, from-cli: true, fromCli: true, inline:
DEBUG! JDLProcessor started with files: src/main/resources/student.jh and options: debug: true, skip-install: false, interactive: false, json-only: false, ignore-application: false, ignore-deployments: false, skip-ui-grouping: false, skip-db-changelog: false, skip-sample-repository: false, skipInstall: false, jsonOnly: false, ignoreApplication: false, ignoreDeployments: false, skipUiGrouping: false, skipDbChangelog: false, skipSampleRepository: false, from-cli: true, fromCli: true
INFO! Found .yo-rc.json on path. This is an existing app
INFO! The JDL is being parsed.
DEBUG! importState exportedEntities: 1
DEBUG! importState exportedApplications: 0
DEBUG! importState exportedDeployments: 0
INFO! Found entities: Student.
INFO! The JDL has been successfully parsed
DEBUG! Applications not generated
INFO! Generating 1 entity.
DEBUG! Generator is starting
Found the .jhipster/Student.json configuration file, entity can be automatically generated!
The entity Student is being updated.
DEBUG! Generator is starting
DEBUG! Time taken to write files: 62ms
create src/main/resources/config/liquibase/changelog/20210202113651_added_entity_Student.xml
create src/main/resources/config/liquibase/fake-data/student.csv
create src/main/java/org/rationaleemotions/domain/Student.java
create src/main/java/org/rationaleemotions/web/rest/StudentResource.java
create src/main/java/org/rationaleemotions/repository/search/StudentSearchRepository.java
create src/main/java/org/rationaleemotions/repository/StudentRepository.java
create src/test/java/org/rationaleemotions/web/rest/StudentResourceIT.java
create src/test/java/org/rationaleemotions/repository/search/StudentSearchRepositoryMockConfiguration.java
create src/test/java/org/rationaleemotions/domain/StudentTest.java
force src/main/resources/config/liquibase/master.xml
DEBUG! Generator has ended
DEBUG! Generator has ended
DEBUG! Deployments not generated
INFO! Congratulations, JHipster execution is complete!
Below is the complete output of my JHipster info command
jhipster info
INFO! Using JHipster version installed globally
INFO! Executing jhipster:info
Welcome to the JHipster Information Sub-Generator
##### **JHipster Version(s)**
##### **JHipster configuration, a `.yo-rc.json` file generated in the root folder**
<details>
<summary>.yo-rc.json file</summary>
<pre>
{
"generator-jhipster": {
"promptValues": {
"packageName": "org.rationaleemotions"
},
"jhipsterVersion": "6.10.5",
"applicationType": "microservice",
"baseName": "necropolis",
"packageName": "org.rationaleemotions",
"packageFolder": "org/rationaleemotions",
"serverPort": "8081",
"authenticationType": "oauth2",
"cacheProvider": "hazelcast",
"enableHibernateCache": true,
"websocket": false,
"databaseType": "sql",
"devDatabaseType": "mariadb",
"prodDatabaseType": "mariadb",
"searchEngine": "elasticsearch",
"messageBroker": false,
"serviceDiscoveryType": "eureka",
"buildTool": "maven",
"enableSwaggerCodegen": false,
"jwtSecretKey": "YourJWTSecretKeyWasReplacedByThisMeaninglessTextByTheJHipsterInfoCommandForObviousSecurityReasons",
"embeddableLaunchScript": false,
"creationTimestamp": 1611077969383,
"testFrameworks": [],
"jhiPrefix": "jhi",
"entitySuffix": "",
"dtoSuffix": "DTO",
"otherModules": [],
"enableTranslation": false,
"clientPackageManager": "npm",
"blueprints": [],
"skipClient": true,
"skipUserManagement": true
}
}
</pre>
</details>
##### **JDL for the Entity configuration(s) `entityName.json` files generated in the `.jhipster` directory**
<details>
<summary>JDL entity definitions</summary>
<pre>
entity Student {
name String,
age Integer
}
microservice Student with necropolis
clientRootFolder Student with necropolis
</pre>
</details>
##### **Environment and Tools**
openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)
git version 2.30.0
node: v14.15.3
yeoman: 3.1.1
Docker version 20.10.0, build 7287ab3
docker-compose version 1.27.4, build 40524192
identical .jhipster/Student.json
INFO! Congratulations, JHipster execution is complete!
When trying to log SQL statements in Django I can see params, duration but not the SQL statement itself. The context parameter sql returns None
I am using MySQL as backend
Settings setup:
DEBUG=True
...
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'formatters': {
'verbose': {
'format': '{levelname} SQL:{sql} {duration} params:{params}',
'style': '{',
}},
'handlers': {
'console': {
'level': 'DEBUG',
'class': 'logging.StreamHandler',
'formatter': 'verbose'
}
},
'loggers': {
'django.db.backends': {
'handlers': ['console'],
'level': 'DEBUG',
},
}
}
Sample output:
DEBUG SQL:None 0.036980390548706055 params:(1,)
So I can the duration, the parameters but not the SQL statements. And I do not know why.
I have based my configuration on https://docs.djangoproject.com/en/dev/topics/logging/#django-db-backends
During a long long search found out this is a bug in version 2.1.4 upgrading to 2.1.5 fixed the problem. I based this on this
https://github.com/jazzband/django-debug-toolbar/issues/1124
Checked and verified. Output after update:
DEBUG SQL:SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED 0.035988569259643555 params:None
I generated demo project from scratch. The project compiled and start with no errors and warns.
But after applying jhipster-entity-audit i'm seeing exception:
2018-01-17 03:46:54.194 WARN 128655 --- [demo-Executor-1] com.zaxxer.hikari.pool.ProxyConnection : HikariPool-1 - Connection org.postgresql.jdbc.PgConnection#409be93d marked as broken because of SQLSTATE(08003), ErrorCode(0)
org.postgresql.util.PSQLException: This connection has been closed.
at org.postgresql.jdbc.PgConnection.checkClosed(PgConnection.java:803)
at org.postgresql.jdbc.PgConnection.getAutoCommit(PgConnection.java:764)
at com.zaxxer.hikari.pool.HikariProxyConnection.getAutoCommit(HikariProxyConnection.java)
at liquibase.database.jvm.JdbcConnection.rollback(JdbcConnection.java:336)
at liquibase.database.AbstractJdbcDatabase.rollback(AbstractJdbcDatabase.java:1166)
at liquibase.lockservice.StandardLockService.acquireLock(StandardLockService.java:205)
at liquibase.lockservice.StandardLockService.waitForLock(StandardLockService.java:170)
at liquibase.Liquibase.update(Liquibase.java:196)
at liquibase.Liquibase.update(Liquibase.java:192)
at liquibase.integration.spring.SpringLiquibase.performUpdate(SpringLiquibase.java:431)
at liquibase.integration.spring.SpringLiquibase.afterPropertiesSet(SpringLiquibase.java:388)
at io.github.jhipster.config.liquibase.AsyncSpringLiquibase.initDb(AsyncSpringLiquibase.java:94)
at io.github.jhipster.config.liquibase.AsyncSpringLiquibase.lambda$afterPropertiesSet$0(AsyncSpringLiquibase.java:77)
at io.github.jhipster.async.ExceptionHandlingAsyncTaskExecutor.lambda$createWrappedRunnable$1(ExceptionHandlingAsyncTaskExecutor.java:68)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
When applying jhipster-entity-audit I selected:
Custom JHipster auditing (works with SQL)
JHipster version: 4.13.3
.yo-rc.json:
{
"generator-jhipster": {
"promptValues": {
"packageName": "com.mycompany.myapp",
"nativeLanguage": "en"
},
"jhipsterVersion": "4.13.3",
"baseName": "demo",
"packageName": "com.mycompany.myapp",
"packageFolder": "com/mycompany/myapp",
"serverPort": "8080",
"authenticationType": "jwt",
"cacheProvider": "ehcache",
"enableHibernateCache": true,
"websocket": false,
"databaseType": "sql",
"devDatabaseType": "postgresql",
"prodDatabaseType": "postgresql",
"searchEngine": false,
"messageBroker": false,
"serviceDiscoveryType": false,
"buildTool": "maven",
"enableSocialSignIn": false,
"enableSwaggerCodegen": false,
"jwtSecretKey": "58737acdea1188e4cf1654fcec9e216448299e87",
"clientFramework": "angularX",
"useSass": true,
"clientPackageManager": "yarn",
"applicationType": "monolith",
"testFrameworks": [],
"jhiPrefix": "jhi",
"enableTranslation": true,
"nativeLanguage": "en",
"languages": [
"en"
]
},
"generator-jhipster-entity-audit": {
"auditFramework": "custom"
}
}
Entity configuration(s):
no entityName.json file
Browsers and Operating System:
Linux Mint 18.3 Sylvia
npm -v
5.6.0
node -v
v8.9.4
Please advice find workaround this issue.
Updated: I opened issue: https://github.com/hipster-labs/generator-jhipster-entity-audit/issues/82
workaround:
tip from #deepu105 for workaround just add string
cm.createCache(com.mycompany.myapp.domain.EntityAuditEvent.class.getName(), jcacheConfiguration);
to CacheConfiguration.java file
I had the same problem when I used IntelliJ for running dev. server.
I don't know why but i resolved it whith this step :
build manually with maven for test if it's an intelliJ bug (for me build is OK) :
./mvnw
got to intellij and open maven pannel : "view" --> "tools windows" --> "maven project"
On "profiles" menu active and desactive and active (again) "IDE" profile (for me "dev" profile is active too)
Now, try to build with intellij.
good luck
I had same problem.
And I realized that because of my dicision using OAuth2.
And I created new jhipster project using HTTP Session Authentication and run project again.
It's OK. Good luck
Overview of the issue
GET /api/account return 500 error when we have ldap integration in jhipster uaa, the user is present in ldap directory not in the uaa DB, therefore it return 500 error, no user found
Motivation for or Use Case
It is a doubt, so my question is should we add the user in DB after successful authentication from Ldap or do I need to update the API according to my requirement, which will be the solution.
Reproduce the error
Add embedded ldap configuration in uaa:
#override
public void configure(AuthenticationManagerBuilder auth) throws Exception {
if (enabled.equalsIgnoreCase("true")) {
ContextSourceBuilder csb = auth.ldapAuthentication().userSearchBase(userSearchBase).userSearchFilter(userSearchFilter).groupSearchBase(groupSearchBase).groupSearchFilter(groupSearchFilter).contextSource();
if (StringUtils.isNotEmpty(root)) {
csb.root(root);
}
if (StringUtils.isNotEmpty(ldapUrl)) {
csb.url(ldapUrl);
}
if (StringUtils.isNotEmpty(ldifFilePath)) {
csb.ldif(ldifFilePath);
}
if (StringUtils.isNotEmpty(manager)) {
csb.managerDn(manager);
}
if (StringUtils.isNotEmpty(managerPassword)) {
csb.managerPassword(managerPassword);
}
} else {
auth.userDetailsService(userDetailsService).passwordEncoder(passwordEncoder());
}
}
When user logs in, the user is verified from ldap directory and after login GET /api/account is trigerred for some information. The user is not present in the uaa app DB, therefore it returns error.
Related issues
Suggest a Fix
JHipster Version(s)
4.3.0
JHipster configuration
Welcome to the JHipster Information Sub-Generator
JHipster Version(s)
/home/varunn/git/etuaa
`-- generator-jhipster#4.3.0
JHipster configuration, a .yo-rc.json file generated in the root folder
{
"generator-jhipster": {
"promptValues": {
"packageName": "com.abc.uaa",
"nativeLanguage": "en"
},
"jhipsterVersion": "4.3.0",
"baseName": "uaa",
"packageName": "com.abc.uaa",
"packageFolder": "com/abc/uaa",
"serverPort": "9999",
"authenticationType": "uaa",
"hibernateCache": "hazelcast",
"clusteredHttpSession": false,
"websocket": false,
"databaseType": "sql",
"devDatabaseType": "h2Disk",
"prodDatabaseType": "mysql",
"searchEngine": false,
"messageBroker": false,
"serviceDiscoveryType": "eureka",
"buildTool": "maven",
"enableSocialSignIn": false,
"enableTranslation": true,
"applicationType": "uaa",
"testFrameworks": [
"gatling",
"cucumber"
],
"jhiPrefix": "jhi",
"skipClient": true,
"nativeLanguage": "en",
"languages": [
"en",
"fr",
"es"
],
"clientPackageManager": "yarn"
}
}
Entity configuration(s) entityName.json files generated in the .jhipster directory
ls: no such file or directory: .jhipster/*.json
Browsers and Operating System
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
git version 2.7.4
node: v8.4.0
npm: 5.3.0
yeoman: 1.8.5
yarn: 0.24.6
Docker version 17.03.1-ce, build c6d412e
docker-compose version 1.14.0, build c7bdf9e
Entity configuration(s) entityName.json files generated in the .jhipster directory
Browsers and Operating System
Chrome and
Ubuntu 16.04