Over at the Apache Commons project, we have two components: Commons Daemon and Commons Crypto.
On top of JAR files, these components produce native binary libraries for various OSs (Windows, macOS, Linux) and are brutally complicated to release. It could be possible to improve these builds using the Docker Maven plugin and some complex POMs, but for now, there are a lot of manual steps. Well, you can't just host any old OS on any old platform due to licensing so it might not be solvable without build agents running on dedicated hardware, for macOS at least. Gary On Sun, Jun 25, 2023 at 5:11 PM Tamás Cservenák <[email protected]> wrote: > > Howdy, > > Multiple times come up on ML questions from users about "multi platform" > deploys/releases, where, AFAIK, some (usually) OS platform > dependant (usually native binary), comes to play. This becomes more and > more requested, for example with GraalVM, where you have to use OS > targeting native code to build native image. > > A real atypical example from the ASF Maven project is maven-mvnd release, > where macOS native binary is being added as manual step (another atypical > problem of mvnd build process is not using remote repository for staging as > none of it lands in Maven Central, but that is a completely different > story). > > So, questions: > - how are people doing it today? > - what can Maven do to help more (if not fully support) this problem? > - where can Maven (or maybe some dedicated existing or new plugin) help > with this problem? > > I'd expect responses from users doing it, how they are doing it, to at > least collect some "common patterns". IF your solution depends on some > vendor (like CI or MRM), it would be okay to mention/explain what it > is, but in general this thread is not meant as "feature comparison" across > vendors. If your regular (by-commit or daily) "snapshot" deploy and > "release" wildly differ, please describe it as well (how and why). > > Ideally, Maven should provide some or maybe even full (vendor neutral, > regarding CI or MRM) support for these patterns. > > Thanks > T --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
