* David Jeske: > On Sun, Aug 25, 2013 at 12:41 PM, Florian Weimer <[email protected]> wrote: > >> * David Jeske: >> > Most of the rest are whole program compilers which must be built on >> system >> > libs from one of those other primary environments. (Ocaml, Go, Haskell, >> D, >> > C++, etc) >> >> For the JVM, there are module systems which try to enforce >> recompilation of all reverse dependencies. It's a PITA for >> large-scale system integrators (particularly if they offer security >> support), but these module systems show that many people do not >> consider this a deal-braker.
> Can you provide a reference? It's hard to find this explicitly in the documentation, but Maven is usually used this way. Dependencies are specified using an exact version (expressing a preference), and by default, the dependencies are "packaged", which is roughly equivalent to shipping a statically linked copy (although the JVM still performs its usual late binding, of course, it's just that the bundled copy is preferred over a system-wide JAR file which might resied in /usr/share/java). <http://books.sonatype.com/mvnref-book/reference/pom-relationships-sect-project-dependencies.html#pom-relationships-sect-dependency-scope> _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
