Removing classifier: jdk17 breaks the project build

Aspose.Words Product Family
1

i upgraded aspose-words from 24.4 to 25.6 in my project

below is the gradle coordinates for 24.4 version

[group: 'com.aspose', name: 'aspose-words', version: '24.4', classifier: 'jdk17'],

below is the gradle coordinates for 25.6 version

[group: 'com.aspose', name: 'aspose-words', version: '25.6', classifier: 'jdk17'],

the project build completed successfully.

Then, i removed classifier: 'jdk17' from the project and built the project.

[group: 'com.aspose', name: 'aspose-words', version: '25.6']

Now , the build failed as below imports were not available.

429×522 22.2 KB

any idea how to fix this? should i update the code in my project so that it uses newer classes in aspose-words:25.6 ?

please advice

2

@divine1 I will consult with our Java developers and get back to you soon.

3

@divine1

The issue stems from removing the classifier: 'jdk17' declaration, which is critical for project functionality. Aspose.Words requires explicit JDK 17 classifier specification. Without it, the default build is downloaded – lacking Java 17-specific classes.

4

@alexey.maslov when will this project and others move to newer classes?

5

@aweech I have sent your question to the developer. He will reply as soon as possible.

6

@divine1

The import error occurs solely due to the missing classifier: 'jdk17' declaration. Restore the classifier in your Gradle configuration – and the existing code will function without modifications. Aspose does not yet consolidate multi-JDK builds into a single artifact, making the classifier mandatory when targeting Java 17.

7

@vyacheslav.deryushev has the developer responded?

8

@aweech Please check previous message from @alexey.maslov.

9

@vyacheslav.deryushev my question is when will this project and the others be moved to newer classes? There are other products on jdk 16. When does Aspose expect to use the latest or at least newer versions?

10

Hi @aweech

We have two classifier for aspose-words: jdk16 and jdk17
Then you use

[group: 'com.aspose', name: 'aspose-words', version: '25.6']

gradle can’t recognise that jdk version of aspose-words you need and skip both.

For fixing this you should choose classifier and use one of that:

[group: 'com.aspose', name: 'aspose-words', version: '25.6', classifier: 'jdk17'] 
[group: 'com.aspose', name: 'aspose-words', version: '25.6', classifier: 'jdk16']

Several years ago we tried to recognise local version of Jdk in aspose-words.pom but many customers complained about wrong jdk version for rare jdk build, and we returned jdk16 and jdk17 classifier.