mshima / generator-jhipster-tenantview

Customization for tenancy and multi-tenancy
9 stars 3 forks source link

"illegal start of expression" when executing gradlew #35

Closed shwabnitz closed 4 years ago

shwabnitz commented 4 years ago

Standard generation with gradle. Jhipster 6.7.1 Tenantview 0.4.4

> Task :compileJava FAILED
<homedir>/data/dev/projects/multi10/src/main/java/com/mycompany/myapp/web/rest/CompanyResource.java:60: error: illegal start of expression
            .headers(HeaderUtil.createEntityCreationAlert(applicationName, , ENTITY_NAME, result.getId().toString()))
                                                                           ^
<homedir>/data/dev/projects/multi10/src/main/java/com/mycompany/myapp/web/rest/CompanyResource.java:81: error: illegal start of expression
            .headers(HeaderUtil.createEntityUpdateAlert(applicationName, , ENTITY_NAME, company.getId().toString()))
                                                                         ^
<homedir>/data/dev/projects/multi10/src/main/java/com/mycompany/myapp/web/rest/CompanyResource.java:123: error: illegal start of expression
        return ResponseEntity.noContent().headers(HeaderUtil.createEntityDeletionAlert(applicationName, , ENTITY_NAME, id.toString())).build();
                                                                                                        ^
3 errors

FAILURE: Build failed with an exception.
shwabnitz commented 4 years ago

Issue still exists.

Saw an issue with $NODE_PATH set wrong for what reason ever. In https://nodejs.org/api/modules.html I read "NODE_PATH is still supported, but is less necessary now that the Node.js ecosystem has settled on a convention for locating dependent modules.". Just to be sure that this is not the source of the issue I deleted the the environment variable but the issue still exists.

Is there something I'm missing?

mshima commented 4 years ago

It’s missing a translation boolean. Jhipster has synchronization problem between generators. For compatibility, I will this this problem only for jhipster 7. Regenerating should fix. jhipster —with-entities

shwabnitz commented 4 years ago

Thank you that works.

If you fix that for jhipster 7 it would be great to receive within the documentation a path to adapt the code already generated.

I assume it is possible to enhance the tenant table with more attributes.

I will make now some more tests. I am happy to enhance the documentation to onboard new users more easy. If you find it appropriate which way do you prefer, doing it in a branch for you to review?

mshima commented 4 years ago

A branch/PR would be great.