...
Open Intellij, and open as a new project. This should automatically index and setup part of the project, but it may equally well set it up incorrectly.
V2.5 (Pre Plugin)
Clone from github.
Open intellij and import from the Exchange Directory (not the modelCatalogueTestPluginApp directory)
Run through the “create module from existing sources” (don’t click any other options)
Open the project in Intellij and go to “Project Settings”
Delete the existing modules
Import a new module, selecting the ModelCatalogueCorePluginTestApp.
Ensure that java 1.8+ is selected, and that the correct groovy and grails libraries are selected - the system should prompt you for these.
At this point the ModelCatalogueCorePlugin should be configured to run:
...
Then you can click on Edit Configurations to get the next screen up: and from there you will need to set up a few environmental variables to get the local system running:
...
Most of these can be left blank, such as the S3 details, as they will default to local default settings if nothing is set, however it is probably wise to configure the JDBC settings.
Also Elastic search needs to be running - ideally on localhost:9300 - if not then change the environment variables as appropriate.
(Plugin Code v2.5)
Key steps to be aware of include:
...
If a module is missing then set it up, click on the + button, and then select the directory (in this case Exchange).
click on wizard option: create module from existing sources
select “grails” from dropdown on next wizard page
finish and apply
Check Project section that Java 1.8 or higher is selected.
Make sure correct Grails version (2.5.6) is selected - right click on Project and select Grails menu option.
If moving from a pre-v2.5 database the role_hierarchy_entry table needs to be dropped, the application will re-apply a new hierarchy on loading up.
-Dgrails.server.port.http=8090 to change port
-Xmx8G to up the heap memory available
...