chore: import dependencies into the source tree, with Lucene artifacts #101
Conversation
There is no need to host many of the customized dependencies of Clouseau in separate repositories as well as produce packages for them separately. They are not used by other applications and they come with a lot of unused parts that are better to be trimmed anyway. The following trees are being added here: - https://github.com/boundary/logula @ `logula_slf4j_2.9.1-2.1.3-p01` - https://github.com/cloudant/JCTools @ 010666e9 - https://github.com/cloudant/overlock @ cf6d7f71 - https://github.com/cloudant/scalang @ 15c8e17b From `JCTools`, only specific classes are included from the `jctools-core` module.
|
Built this and ran With this change, can/should the existing Lucene code scanner be pointed to this repo? |
Mind that only the Lucene JARs are imported in the PR, not the source code. I think the code scanner has to interact with the sources themselves. |
pgj
force-pushed
the
import-dependencies+lucene-jars
branch
from
ae465e3 to
d219ef7
Compare
|
Apparently I made a mistake... I did not add the change for |
Nice save! Seeing this now: Search suite tests still passing 😅 |
pgj
force-pushed
the
import-dependencies+lucene-jars
branch
4 times, most recently
from
a596c88 to
d219ef7
Compare
pgj
force-pushed
the
import-dependencies+lucene-jars
branch
from
d219ef7 to
60d75fe
Compare
|
Closing in favor of #102. |
This is a potential variation on #100 with artifacts for Apache Lucene included in the tree.