xjlgod opened a new issue, #6888:
URL: https://github.com/apache/incubator-seata/issues/6888

   <!-- Please do not use this issue template to report security 
vulnerabilities but refer to our [security 
policy](https://github.com/seata/seata/security/policy). -->
   
   - [x] I have searched the [issues](https://github.com/seata/seata/issues) of 
this repository and believe that this is not a duplicate.
   
   ### Ⅰ. Issue Description
   When I use idea to read file.conf in resources. it is ok.
   <img width="1122" alt="f4a5e259cb931496979e16d5ce4f5c22" 
src="https://github.com/user-attachments/assets/7740ba4e-2c6f-4cfd-8f7a-dfc8dda2a8b4";>
   
   When I package server, it can not read file.conf in right path.
   <img width="1280" alt="4b3dd01a1638c4eab39e5cc9fc706d25" 
src="https://github.com/user-attachments/assets/96cf6520-9833-4660-9cdc-0f760a3e9009";>
   
   ### Ⅱ. Describe what happened
   
   I think there are some errors after package, then change the result in here .
   
![image](https://github.com/user-attachments/assets/ec44f3b6-586a-4275-a9da-68b37f0df3f7)
   
   
   ```
   Just paste your stack trace here!
   ```
   
   
   ### Ⅲ. Describe what you expected to happen
   
   
   ### Ⅳ. How to reproduce it (as minimally and precisely as possible)
   
   1. xxx
   2. xxx
   3. xxx
   
   Minimal yet complete reproducer code (or URL to code):
   
   
   
   ### Ⅴ. Anything else we need to know?
   
   
   ### Ⅵ. Environment:
   
   - JDK version(e.g. `java -version`):
   - Seata client/server version:  
   - Database version:
   - OS(e.g. `uname -a`):
   - Others:


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