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

SDK and JRE images should only contain production shared libraries #17

Closed
pshipton opened this issue Dec 12, 2017 · 0 comments · Fixed by #210
Closed

SDK and JRE images should only contain production shared libraries #17

pshipton opened this issue Dec 12, 2017 · 0 comments · Fixed by #210

Comments

@pshipton
Copy link
Member

pshipton commented Dec 12, 2017

There are a number of extra shared libraries in the SDK and JRE images. Only the required libraries should be included in these images.

  • libjclse9_29.so is only for Java 9 and should just be excluded

  • libgdb_j929.so is for development/debugging and should be put elsewhere

  • the following are for testing, and should be put into another location so they can be used by the tests: libSharedClassesNativeAgent.so, libballoon29.so, libbcuwhite.so, libbcvwhite.so, libgptest.so, libhooktests.so, libj9ben.so, libj9lazyClassLoad.so, libj9thrnumanatives29.so, libj9thrtestnatives29.so, libj9unresolved.so, libj9vmtest.so, libjcoregen29.so, libjlmagent29.so, libjniargtests.so, libmemorywatcher29.so, libmigration.so, libosmemory29.so, libsoftmxtest.so, libtestjvmtiA.so, libtestjvmtiB.so, libtestlibA.so, libtestlibB.so, libvmruntimestateagent29.so

Moving the test libraries needs to be coordinated with the test team since the tests will need to find the libraries in the new location. eclipse-openj9/openj9#805

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

Successfully merging a pull request may close this issue.

1 participant