Use plugin and don't package public libs inside jar

Hi, I have a package testing

<dependency>
            <groupId>com.aspose</groupId>
            <artifactId>aspose-total</artifactId>
            <version>25.4</version>
            <type>pom</type>
        </dependency>

and here is a HUGE problem, you package org.bouncycastle inside you lib. You SHOULD shadow this public package or provide dependency of it as external library. Otherwise it could BROKE enterprise code where you lib is used.

here is a plugin that do it for you https://maven.apache.org/plugins/maven-shade-plugin/

bcprov_aspose.png (95.2 KB)

@valenpo,

Thanks for the screenshot and details.

I tested your “pom.xml” in an Eclipse project to install the Aspose.Total for Java 25.4 libraries. I even tried the latest Aspose.Total for Java 25.8. Upon review, I found that “org.bouncycastle” is included only within the Aspose.OMR for Java JAR, while other JARs do not contain it. We appreciate you bringing up this matter and sharing your suggestions. We will investigate the issue further and update you soon.

Hello, @valenpo

I am a developer for Aspose OMR for Java. I will look into it and post results here.

Hello, @valenpo

Thank you for your patience!

Fix for this issue is ready and available in 25.9 version of Aspose OMR for Java and will be in the next Total release.