Are there any release notes for Aspose.Barcode for Java 4.4.0?
Switching to the new version is not really smooth, since many methods and fields had their names changed slightly. I could figure out most of it, but in the jar I cannot find the class GraphicsUnit, that is supposed to hold the int constants. Can I just use the class from version 2.7.0, or have the values changed?
Hi,
Thank you for your inquiry.
The base code for Aspose.BarCode for Java v4.4.0 is exactly the same as of Aspose.BarCode for .NET v4.4.0. That means Aspose.BarCode for Java has all the bug fixes and features that are included in it’s equivalent .NET version plus some of it’s own. You can get the release notes of Aspose.BarCode for Java v4.4.0 from links shared above.
Regarding the GraphicsUnit class, I am afraid, I’m unable to find it in v4.4.0. I will check with development team regarding this issue.
Hi,
It is regarding the missing GraphicsUnit class in latest version of Aspose.BarCode for Java v4.4.0. I have attached this thread to the appropriate issue (Id:33117) from our bug tracking system. You will be notified automatically once this issue is resolved.
We apologize for your inconvenience.
The issues you have found earlier (filed as BARCODJAVA-33117) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
This class is missing in Aspose Barcode 5.4.1 for Java.
Hi Vladimir,
Thanks for your inquiry. I’m sorry to share with you that I managed to replicate the problem. I have logged this problem under ticket id BARCODJAVA-33336 in our issue tracking system. Your request has also been linked to this issue and you will be notified as soon as it is resolved and available for the public use. We’re sorry for your inconvenience.
Hi, Imran.
This issue is still presented in recently released java Aspose Barcode 5.6.2-jdk16 version.
Hi Vladimir,
Thanks for your inquiry. I’m sorry to share with you that this issue ( BARCODJAVA-33336 ) is not yet resolved. This issue is pending for analysis. I have asked the responsible developer to take a look at this issue shortly. As soon as any information is shared by him, I will be more than happy to share that with you.
We’re sorry for your inconvenience.