Chris Beams 8b30c22d6e Move bisq.core{=>.app}.CoreModule ... There are two structural / organizational reasons for this move: 1. References from one package to another should always be upward or lateral, never downward, as the latter causes package cycles (aka 'tangles') which damage the suppleness and understandability of a large codebase. Prior to this change the high-level bisq.core.CoreModule class imported many classes from child packages like bisq.core.{btc,dao,user,util}, etc. By moving CoreModule down into the '.app' package, it can reference all these other packages as siblings instead of doing so as a parent. 2. the bisq.core.desktop and bisq.core.app packages are the only locations that reference the CoreModule class. By moving the class into bisq.core.app, greater cohesion is acheived, again making the codebase that much easier to read and understand.		2020-01-20 12:07:43 +01:00
..
package	Add command for signing windows executables with the default code signing certificate	2019-12-10 12:27:58 +01:00
src	Move bisq.core{=>.app}.CoreModule	2020-01-20 12:07:43 +01:00