The GitHub Actions job "CI" on grails-core.git/fix/forge-security-user-nullable-8.0.x has failed. Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run: a0f15f6c1a1c1cfe0189118ca177691f98bac874 / Scott Murphy Heiberg <[email protected]> Map the security User through the directive its data store understands The template emitted `table 'users'` for every data implementation, but `table` is a Hibernate directive. On MongoDB it was silently ignored, so the intent behind it -- don't name the persistence unit `user`, which is a reserved word in PostgreSQL, H2 and SQL Server -- was lost exactly where nothing warned about it. Booting a generated mongodb app showed the documents landing in a `user` collection; with `collection 'users'` they land in `users`. Pick the directive from the selected features, the way GrailsBase and DatabaseMigrationPlugin already do, rather than from the gorm option, so it holds whether the implementation was chosen with --data or by naming the feature. Hibernate 5 and 7 keep `table 'users'`, MongoDB gets `collection 'users'`, and a store that uses neither -- Neo4j -- gets no mapping block at all rather than a directive it does not understand. Report URL: https://github.com/apache/grails-core/actions/runs/33549636955 With regards, GitHub Actions via GitBox
