ankitshokeen commented on issue #15336:
URL: https://github.com/apache/dubbo/issues/15336#issuecomment-2831143532

   > Hi [@ankitshokeen](https://github.com/ankitshokeen), thanks for the report 
and your willingness to contribute!
   > 
   > Just a quick clarification: running `mvn clean install` will not trigger 
service registration to Nacos, because Dubbo only registers services at 
runtime, when the application is actually started (e.g., via `java -jar`,` 
main()` method in IDE, or `Spring Boot startup`).
   > 
   > The `mvn clean install` command is purely for building the project — 
compiling, running tests, packaging, and installing artifacts into the local 
Maven repository. It does not run your service or trigger any registry behavior.
   > 
   > If you’re expecting the service to register itself to Nacos, please try 
running the application (after mvn clean package) and then check the Nacos 
console to verify the service is properly registered.
   > 
   > Let me know if you're still seeing errors during build or at runtime — 
feel free to share stack traces or configs, and I’d be happy to take a deeper 
look!
   > 
   > Thanks again!
   
   Hi @heliang666s ,
   
   Thanks for the helpful explanation that really clears things up!
   
   I now understand that service registration with Nacos only occurs when the 
application is actually running, not during the build process with mvn clean 
install. I’ll go ahead and run the application after packaging it and check the 
Nacos console for any registered services.
   
   Also, could you please let me know which module in the project I should 
start to test the Nacos service registration?
   
   I’ll be sure to share any errors or configurations if I encounter issues 
during runtime. Appreciate your support!
   
   Best regards,
   Ankit


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to