Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Native methods should not be relocated in the Java code #542

Open
maguro opened this issue Jan 27, 2020 · 3 comments
Open

Native methods should not be relocated in the Java code #542

maguro opened this issue Jan 27, 2020 · 3 comments
Labels

Comments

@maguro
Copy link
Contributor

maguro commented Jan 27, 2020

Shadow Version

5.2.0

Gradle Version

5.6.4

Expected Behavior

Native functions should not be relocated in the Java code that's being relocated. The shared libraries' functions are hard coded and so native functions should not be relocated.

Actual Behavior

Native functions are being relocated in the Java code that's being relocated.

@boroczkigabor
Copy link

Have you found any workaround for the issue? I'm seeing the same behavior with rocksdbjni using automatic relocation. The Java classes are moved to the shadowed package, but the natives are not.

@maguro
Copy link
Contributor Author

maguro commented Apr 9, 2021

If your question was directed toward me, haven't. Sorry.

@Goooler Goooler changed the title Shading dependencies with native libraries Native methods should not be relocated in the Java code Jan 26, 2025
@Goooler Goooler added the bug label Jan 26, 2025
@Goooler
Copy link
Member

Goooler commented Feb 27, 2025

Any reproducer for this? I'm planning to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants