I’m integrating the Aspose.Words for Java library into an existing technology stack of a large application. We have a standard practice to repackage any 3rd party libraries such as aspose-words-18.11-jdk16.jar, and add any additional files required.
- Extract the aspose-words-18.11-jdk16.jar into a work dir
- Add additional files to work dir (these go into the root dir of the new archive):
- Aspose.Words.lic
- thirdpartylicenses-Aspose.Words for Java.txt
- README_aspose-words.txt (custom README file required for all 3rd party libraries within our techstack)
- Create a new JAR named aspose-words.zip of the work dir
- JARs are signed by our own application
The same steps would be performed when a new Aspose.Words for Java version is released by Aspose. For easier updates to our application, the library file name is changed to aspose-words.zip so only the new revision of this file needs to be installed.
Reading up on the EULA, I’m thinking only the following paragraph relates to the above practice:
2.5. Disassembly. You may not reverse engineer, decompile, disassemble or in any other way try to gain access to information regarding the construction of the Product(s).
In my view, we’re not disassembling the Aspose.Words for Java to for that purpose. To ensure we are compliant with the EULA, kindly confirm the following:
- Is it allowed to repackage the Aspose.Words for Java as described above?
- Is it allowed to rename / redistribute Aspose.Words for Java as aspose-words.zip instead of aspose-words-18.11-jdk16.jar?