AppJars
|
Is the source available? Our team is not comfortable adopting a closed-source dependency this deep in the stack without being able to read it when something goes wrong. |
Replies: 1 comment
|
Yes, for reading and debugging. Every AppJar publishes its What that does not include is the right to build derivative works from it, redistribute it, or publish modifications — the grant covers internal debugging, education and review. The terms are in the License Agreement. So the practical answer to "can we read it when something goes wrong" is yes. The module repositories themselves are private, which is why there is no source code in this organization and no pull requests against the AppJars. One thing that is open source and worth knowing about, since it covers the integration surface where most problems actually happen: every AppJar has a Demos accept issues and pull requests. If the wiring in one is wrong or out of date, that is a fix we want. If you find a defect in an AppJar itself, it goes in the public tracker — free and paid users report there under the same rules, and fixing defects is part of the product rather than a paid service. |
Yes, for reading and debugging. Every AppJar publishes its
-sources.jaralongside the binary, so you attach sources in your IDE the same way you would for any other dependency, step through our code in a debugger, and read exactly what is happening when something misbehaves.What that does not include is the right to build derivative works from it, redistribute it, or publish modifications — the grant covers internal debugging, education and review. The terms are in the License Agreement.
So the practical answer to "can we read it when something goes wrong" is yes. The module repositories themselves are private, which is why there is no source code in this organization and no pull request…