Consider separating the package structures for bramble-java and bramble-core
Consider using a separate package for bramble-java
(e.g. org.briarproject.bramble.java.*
)
Currently, bramble-java
provides the same packages as bramble-core
.
Some bramble-java
classes extend package-private classes from bramble-core
(mostly in bluetooth). Hmm ....
When briar is going to use java >= 9 and provides modules this needs to be addressed anyway. (I believe briar should be around for many, many new java versions to come ;-)