| 1 |
On 12/07/2020 16:42, Zhang Zongyu wrote: |
| 2 |
> The reason why I have to install binaries varies. Here are the main reasons: |
| 3 |
> 1. Maven central only distributes binary jars (even those jars are |
| 4 |
> named with a "sources" suffix). I will fix the problem by changing the |
| 5 |
> SRC_URI of a proper source code file next week. |
| 6 |
|
| 7 |
Could you show me a sources jar that doesn't contain sources? Just |
| 8 |
curious, I've never ran into any. |
| 9 |
|
| 10 |
In principle, a Maven repository can contain any files, so it's |
| 11 |
possible, but in general, if a project uses Maven sources plugin, the |
| 12 |
jar should contain sources just right. Those sources however aren't |
| 13 |
intended to be compiled on their own, they serve as documentation or are |
| 14 |
used for IDE autocomplete. |
| 15 |
|
| 16 |
You'd need to checkout the project's repository (including the build |
| 17 |
tools) to be able to build the project in general. |
| 18 |
|
| 19 |
> 2. The source code files are not written in Java. Some Jars contain |
| 20 |
> Ruby, Scala, Kotlin, or Lombok codes. [3] Maybe we should discuss how |
| 21 |
> to emerge those packages next week. |
| 22 |
|
| 23 |
Just a note, Lombok isn't a language, but Java compiler plugin that |
| 24 |
generates bytecode from annotations at compile time. |
| 25 |
|
| 26 |
Scala and Kotlin are a common sight, as they compile into the same |
| 27 |
bytecode that JVM can run. |
Archives