Am 26.12.22 um 19:37 schrieb Damjan Jovanovic:
On Fri, Dec 2, 2022 at 9:10 PM Jim Jagielski <j...@jagunet.com> wrote:
There are some java apps that no longer support ant and
instead rely on maven. Last I checked, I don't think we
support that, do we?
But why are we compiling Java projects?
We compile C/C++ projects because (1) upstream often doesn't provide
binaries, and/or (2) we need to patch the source.
For Java projects, (1) is almost universally false, and (2) is often false.
Why can't we just download and use the upstream .jar files in those cases,
instead of needing Maven to build the source ourselves?
I think we should not build any dependencies if we rebuild AOO.
If we create a release build then we should have stashed the dependencies.
In case of Java files this is easy because we can use JAR files as you
suggested.
For C++ dependencies we should build a repository with maven like tools
like conan [1] Maybe even build an own Maven Repository for all if this
is possible.
However, We should also look into the software Architecture that we can
handle different Versions of One dependency, or can switch to concurrent
libraries without much maintenance work. Going more in the direction of
Clean Code Architecture.
All the best
Peter
[1] https://conan.io/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
