LJX2017 commented on issue #4045: URL: https://github.com/apache/texera/issues/4045#issuecomment-3583255436
> This idea is good. IntelliJ's built-in Compound also works fine for me. I don't see any dependencies that prevent any microservice from running. There are some dependencies between microservices during the runtime, but we can always wait until all microservices are ready before we open Texera. I initially tried to follow the recommended startup order for the microservices: ```If one microservice failed after running, it may have dependency to another microservice, so wait for other ones to start``` However after testing, I agree that the microservices don't have hard startup dependencies. I will switch to using IntelliJ’s built-in Compound configuration for launching the microservices. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
