github-actions[bot] commented on issue #15344:
URL: 
https://github.com/apache/dolphinscheduler/issues/15344#issuecomment-1864113320

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   1. The --class-path parameter is hard-coded in the project, but it is not 
very friendly to users using JDK8 because JDK8 does not have this option.
   2. The packaged jar package can obviously be run locally, but in the Java 
component of DolphinScheduler, it keeps reporting an error that the main class 
cannot be found or cannot be loaded.
   3. When using the jar running type, why do you choose the main package? You 
must also select the resource center, otherwise it will not run. It feels like 
a repeated selection.
   
![4503F3E75B2D2B2F948D23C995797B02](https://github.com/apache/dolphinscheduler/assets/100180734/7637fc3a-f042-4ec5-9c38-1c792240f8f7)
   
   
![7F8F3393213B8A42A03A85B0A8DA73EC](https://github.com/apache/dolphinscheduler/assets/100180734/d980df09-276e-41f5-a34d-d53390f64d8e)
   
   
   ### What you expected to happen
   
   The Java component is not friendly enough. I originally thought that the 
things in the resource center could be reused, but in the end I still had to 
use the shell component, and then put the jar and sh on each worker regularly. 
It was too troublesome.
   
   ### How to reproduce
   
   Just use the Java component, and the resource center uses HDFS storage.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.2.x
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)


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

Reply via email to