1 |
Hi Zongyu, |
2 |
|
3 |
Zhang Zongyu <zzy2529420793@×××××.com> writes: |
4 |
|
5 |
> This week I mostly worked on the java-pkg-simple.eclass.[1] |
6 |
> |
7 |
> I tried to make use of the variables listed in java-ebuilder, including |
8 |
> ${JAVA_TEST_SRC_DIRS}, ${JAVA_RESOURCES_DIRS}, |
9 |
> ${JAVA_MAIN_CLASS}, and so on. |
10 |
> Besides, there are two more variables in the eclass called |
11 |
> ${JAVA_BINJAR_FILENAME} and ${JAVA_LAUNCHER_FILENAME}. |
12 |
> ${JAVA_BINJAR_FILENAME} indicates the binary file that will be |
13 |
> compared with our natively compiled jar file, and it also enables the |
14 |
> possibility to install itself directly, which may help us avoid circular deps. |
15 |
> ${JAVA_LAUNCHER_FILENAME} specifies the name of the launcher |
16 |
> script for the jar, it works together with ${JAVA_MAIN_CLASS}. |
17 |
> You can test the new eclass by emerging "java-ebuilder::spark-overlay" |
18 |
> and "dev-java:commons-io:0". [2] |
19 |
|
20 |
Good. |
21 |
|
22 |
> Also, there are some bugfixes for java-ebuilder, which you can check in [3]. |
23 |
> |
24 |
> I hope that the eclass is working well and if it is going well we may start |
25 |
> to go through the review process this week. |
26 |
|
27 |
OK, please push through the review process ASAP. |
28 |
|
29 |
Yours, |
30 |
Benda |