Does the aspose-pdf-10.9.0.jar really have to be 33 MB? It nearly doubled the size of my deployment EAR. What the heck is in there? In contrast, aspose-cells-8.6.2.jar is only 6 mb.
Hi Ken,
- aspose.pdf (legacy Aspose.Pdf for Java)
- com.aspose.pdf (new Document Object Model for PDF file creation and manipulation).
- com.aspose.pdf.kit (legacy Aspose.Pdf.Kit for Java)
Hi, is there any way to remove legacy parts from jar manually? Or maybe you can build separate jar file without legacy code. We was going to migrate to Aspose.PDF from other library, which is less then 3Mb in size, and now worrying about twice grow of the size of our distribution. Thanks
Hi John,OneVizion_VENDOR:Hi, is there any way to remove legacy parts from jar manually? Or maybe you can build separate jar file without legacy code. We was going to migrate to Aspose.PDF from other library, which is less then 3Mb in size, and now worrying about twice grow of the size of our distribution. Thanks
Hi, any news on this? Our release date is close, we need to know if we can do something with this, or prepare to deploy twice larger jars.
Hi John,
Hi there,
Any progress on this?
Thank you.
Kind regards,
Rui Rodrigues
@rmrodrigues,
We have removed all legacy packages and the size of Aspose.Pdf Jar is not downgraded significantly, because we have added a lot new features and enhancements. However, we optimize the size of the Jar and it is a continuous activity. Please download and try the latest version 17.9 of Aspose.Pdf for Java API.
44MB is ridiculous for this jar - it was 33mb last year when we started this thread about how big it was. I have a 40k line application that’s not this big. This one “utility” jar doubles the size of my deployment. Your excel plugin is only 16mb - how can the pdf plugin be twice that size? Something’s fishy here. Your excel plugin was 6mb last year, now it’s 16??? You guys need to go on a code diet. I’m going to start looking for something much lighter weight.
@KenOtwell,
Kindly list down all details of the usage of Aspose.Pdf for .NET API in your applications. We will discuss this matter with our product team, and then let you know about the outcomes.