Lazily looks good to me... :D Can you add a link or explain a bit more what this buys us.
Thank you! On Fri, Apr 23, 2021 at 8:43 PM Konstantin Gribov <[email protected]> wrote: > Hi, folks. > > I hope for comments and kind of lazy consensus. If there would be no > objections I'll merge it to main and branch_1x. > > I created tika-bom modules with bill-of-materials (in Apache Maven > terminology) / platform (for Gradle users). It will allow easy Tika module > versions alignment and to write Tika it once when importing BOM. > > Downside is that adding a new downstream-consumable module (like another > parser one) will require to not forget to add it to tika-bom. > > BOMs are both for 2.x [1, 2] and 1.x [3, 4] branches. > > In case of 1.x tika-bom includes almost all artifacts useful as > dependencies in downstream projects. So Tika end user applications like > tika-server and tika-app shouldn't be included. > > For 2.x mostly the same (but much more modules xD). Also included artifacts > like eval-core, server-core etc. Tika Pipes are in separate bom (tika-pipes > pom module itself). > > [1]: https://issues.apache.org/jira/browse/TIKA-3367 > [2]: https://github.com/apache/tika/pull/431 > [3]: https://issues.apache.org/jira/browse/TIKA-3368 > [4]: https://github.com/apache/tika/pull/432 > > -- > Best regards, > Konstantin Gribov. >
