Hello,

This week I mostly worked on the java-pkg-simple.eclass.[1]

I tried to make use of the variables listed in java-ebuilder, including
${JAVA_TEST_SRC_DIRS}, ${JAVA_RESOURCES_DIRS},
${JAVA_MAIN_CLASS}, and so on.
Besides, there are two more variables in the eclass called
${JAVA_BINJAR_FILENAME} and ${JAVA_LAUNCHER_FILENAME}.
${JAVA_BINJAR_FILENAME} indicates the binary file that will be
compared with our natively compiled jar file, and it also enables the
possibility to install itself directly, which may help us avoid circular
deps.
${JAVA_LAUNCHER_FILENAME} specifies the name of the launcher
script for the jar, it works together with ${JAVA_MAIN_CLASS}.
You can test the new eclass by emerging "java-ebuilder::spark-overlay"
and "dev-java:commons-io:0". [2]

Also, there are some bugfixes for java-ebuilder, which you can check in [3].

I hope that the eclass is working well and if it is going well we may start
to go through the review process this week.

Regards,
Zhang Zongyu

[1] the modified java-pkg-simple.eclass
https://github.com/6-6-6/spark-overlay/blob/master/eclass/java-pkg-simple.eclass
[2] ebuild of dev-java/commons-io using java-pkg-simple
https://github.com/6-6-6/spark-overlay/blob/master/dev-java/commons-io/commons-io-2.6-r1.ebuild
[3] java-ebuilder
https://github.com/6-6-6/java-ebuilder