Sorry for the inconvenience. At this moment in the pom file for the aspose-email library specified the version that are stored in our slim sample here. This jar file applies to the classifier jdk16, because our Viewer for Java can be used with Java 6 version, but you can also specify other versions of classifier or versions of Aspouse libraries for testing our product. Basically we specify in our library, the Aspose libraries which was tested and satisfied our requirements.
If you will have more questions please feel free to contact us.
Thank you for your clarification. But we use in our samples the Aspose library from Aspose web site . After downloading this library you will see two jar files with 5.0.0.0 version stored in the package as shown on the screenshot. And how I said earlier, it is the sample and you can change independently the versions of library in it.
I think this is a mistake from Apose then. As you can see the versionnumber of the zipfile is 5.0.0…
And in their maven repository they are using this versionnumber as well. Now I have to manually change the version in your poms. I think it would be better/easier if you stick to the maven version numbers as used by Apose.
Any suggestion how I can specifically use and specify the jdk16 of jdk17 versions as used by the Aspose libraries in maven?