not sure we're on the same understanding. I'll try to focus on 2 specific topics
Le jeudi 14 février 2019, 22:57:26 CET Emmanuel Bourg a écrit : > > - Are you making clear that you're not using the official Maven > > distribution, e.g. by adjust the info from 'mvn --version'? > > No we aren't, but that's worth considering. Note that as the Maven > reproducibility improves this will become unnecessary because at some > point we'll be able to build binaries strictly identical to the Apache ones. IIUC you don't use the same versions of dependencies (because of uniqueness of each lib in Debian [1]) as those used in a "normal unconstrained" build from source [2] [1] https://salsa.debian.org/java-team/maven/blob/master/debian/maven.links [2] https://maven.apache.org/ref/3.6.0/apache-maven/dependencies.html#Project_Transitive_Dependencies I don't yet understand the details of Debian build system, if the symlinks are used at build time or only at runtime, but even if you the resulting jars of the Debian build from Maven source are the same binaries, the execution of Maven does not run with the same dependencies, then there may be subtle differences during the run (for example from jansi, or guice, or commons-cli or ...) IIUC, that uniqueness of every library is a Debian principle, then a Maven distribution from Debian cannot be equivalent to a "normal" distribution where library versions are purely selected by Maven source's pom.xml, without adding any constraint This is why having Debian's distribution display its name in "mvn -v" would make that more clear. > > - What is the optimum way of distributing Maven sources? For example: > > also providing compile and package scripts (instead of calling > > maven-plugins)? > > The current system is mostly fine to us. The only issue I got recently > was the embedding of the SLF4J sources at build time, because we don't > build binary packages installing the sources artifacts of the libraries > and they aren't available at build time (we could though, that's a > little more work). In this case I patched the build [4] to embed the > compiled classes with the shade plugin instead (the patch was refused > though [5], but that's a fairly minor divergence). Let's discuss a little bit about plugins: when Debian launches the "mvn" command to build some Debian package, does it use Maven Central like anybody? = where do the Maven plugins used during build come from? Regards, Hervé --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
