Dragas
Dragas
This should be a pull request.
Hmm, I agree. There are some issues with V3 as well. For example I can't switch channels and need to use legacy methods to setup monitor mode.
JLink comes to mind. Automatic module usage prevents usage of jlink.
> Rant: JPMS is a bad module system because it doesn’t support splitting a package. It’s perfectly reasonable for a package to grow over time as its project grows. And...
I doubt reflectively calling `Module` class will solve the issue, considering `open` declaration in module definition is what permits reflective operations against module exposing a package. See the following for...
@davsclaus it seems that CAMEL-13001 does not exist on that tracker. Did it get renamed?
@edenman Sometimes such artifacts happen using `ViewPager` with non-standard page width, for example `7%` of the view's width.
Read: [Calling native code from javascript in react native](https://facebook.github.io/react-native/docs/native-modules-android.html).
I don't seem to depend on manually configured `LocalContainerEntityManagerFactoryBean` but I'll keep it in mind.