Search before asking

• I had searched in the issues and found no similar feature requirement.

Motivation

Right now, we support two kind of usage of JAVA tasks,

The first type is JAVA, user can write java code, once the worker receive this kind of task, it will compile the java code to class, and then execute the class file.

The second type is JAR, user can submit a fat jar, once the worker receive this kind of task, it will directly execute the fat jar.

This issue is want to remove the first type of JAVA task, since this is more like a demo, no one will submit java code, and in most of the time, the java application is not written within one file.

So we only need to support submit Jar.

Design Detail

Further more, we would better support user submit jars rather than a fat jar. The command may look like below, this should be more usefully

java $JAVA_OPTS \
  -Dxx.yy.args=1 \
  -cp "xx.jar":"xx.conf" \
  xx.Application args

So we need to change the current task mode into: Fat JAR, NORMAL JAR

Compatibility, Deprecation, and Migration Plan

This is not compatible with the current version.

Test Plan

Add unit test.

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct