You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if you have a mvn project with modules, such as
project
\- module1 (with the normal structure of a kalix service)
\- pom.xml
Running mvn kalix:runAll on module1 works as expected. However, if running on the IDE, it will not pickup the correct logback-dev-mode.xml nor will it start the docker-compose.yml. To do it, the user will need to add this to the VM options in the IDE running config: -Dlogging.config=module1/src/main/resources/logback-dev-mode.xml -Dkalix.dev-mode.docker-compose-file=module1/docker-compose.yml
I think we should be able to correctly pick up both the config and the docker-compose file by default.
The text was updated successfully, but these errors were encountered:
We can detect that we are running on dev-mode and look up files at the root of the project, but we assumed that the project root will always be the same as the process root.
When we run the main function, we can't know where is the process root and we can't know where is the main located. Is it under module1 or module2? Which directory should we append to src/main/resources?
Currently, if you have a mvn project with modules, such as
Running
mvn kalix:runAll
onmodule1
works as expected. However, if running on the IDE, it will not pickup the correctlogback-dev-mode.xml
nor will it start thedocker-compose.yml
. To do it, the user will need to add this to the VM options in the IDE running config:-Dlogging.config=module1/src/main/resources/logback-dev-mode.xml -Dkalix.dev-mode.docker-compose-file=module1/docker-compose.yml
I think we should be able to correctly pick up both the config and the docker-compose file by default.
The text was updated successfully, but these errors were encountered: