petrov-mg commented on issue #10907:
URL: https://github.com/apache/ignite/issues/10907#issuecomment-1703790832
Oh. Got it. You are using `maven-assembly-plugin` to repackage Ignite JARs
and your project's JARs in one Uber-JAR
```
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<appendAssemblyId>false</appendAssemblyId>
<descriptorRefs>
<descriptorRef>jar-with-dependencies</descriptorRef>
</descriptorRefs>
<archive>
<manifest>
<mainClass>io.github.quickmsg.jar.JarStarter</mainClass>
</manifest>
</archive>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
</plugin>
```
As a result, Ignite treats your project's classes as Ignite internals and
unconditionally applies security checks to them.
You can try to avoid using Uber-JAR to solve this problem. Are there good
reasons why you need Uber-JAR?
In any case, I'll see if we can improve the security check in this case.
Tank you for reporting this issue.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
