Hello,
We deliver 3rd party
jar material in our own jar file. In essence, we un-jar the 3rd party jar
files and re-jar into one jar file that we distribute with our product.
When we do this with the aspose jar file (aspose-cells-2.4.1.jar), we are unable
to compile our code.
Referencing the
aspose-cells-2.4.1.jar file as part of the classpath, it works. Our
preference is to do the re-jarring into one jar file rather than deliver
different jar files as part of our product.
Is this
possible? Or does Aspose lock down the jar files with a binary
signature?
Thanks,
--Bill
Cowden
This message was posted using Email2Forum by ShL77.
<!–[if gte mso 10]>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
<![endif]–>
Hi,
Well,
Aspose.Cells for Java jar file has its own digital signatures, and hence, I am afraid it should not be re-jar.
Thank you.