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

Option to have native libraries in separate directory, not visible in classpath #62

Open
vkopichenko opened this issue Dec 4, 2017 · 0 comments

Comments

@vkopichenko
Copy link

vkopichenko commented Dec 4, 2017

Currently both classpath and java.library.path are determined by single setting <repositoryName>lib</repositoryName>.

It would be nice to have them separate like this:

<libDir>lib</libDir>
<nativeDir>bin</nativeDir>

This would prevent classpath scanning problems like this:
ronmamo/reflections#80

15:41:53.023 [WrapperSimpleAppMain] WARN  org.reflections.Reflections - could not create Vfs.Dir from url. ignoring the exception and continuing
org.reflections.ReflectionsException: could not create Vfs.Dir from url, no matching UrlType was found [file:/opt/ecp/lib/wrapper-windows-x86-64.dll]
either use fromURL(final URL url, final List<UrlType> urlTypes) or use the static setDefaultURLTypes(final List<UrlType> urlTypes) or addDefaultURLTypes(UrlType urlType) with your specialized UrlType.
        at org.reflections.vfs.Vfs.fromURL(Vfs.java:108)
        at org.reflections.vfs.Vfs.fromURL(Vfs.java:90) 
        at org.reflections.Reflections.scan(Reflections.java:236)
        at org.reflections.Reflections.scan(Reflections.java:203)
        at org.reflections.Reflections.<init>(Reflections.java:128)

This feature is also requested at https://stackoverflow.com/questions/34334599/appassembler-maven-plugin-how-to-include-native-library-files-when-generating.

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

No branches or pull requests

1 participant