5d6259a973
All JARs in $pkg/share/java (for each $pkg in the build inputs) are added to $CLASSPATH. Thus, you can say buildInputs = [ setJavaClassPath someJavaDependency ]; and the JARs in someJavaDependency will be found automatically by tools like javac or ant. Note that the manual used to say that JARs should be installed in lib/java; this is now share/java, following the Debian policy: http://www.debian.org/doc/packaging-manuals/java-policy/x110.html The directory share/java makes more sense because JARs are architecture-independent. (Also, a quick grep shows that we were not exactly consistent about this in Nixpkgs.) |
||
|---|---|---|
| .. | ||
| build-fhs-chrootenv | ||
| buildenv | ||
| builder-defs | ||
| cabal | ||
| clang-wrapper | ||
| dotnetenv | ||
| fetchbzr | ||
| fetchcvs | ||
| fetchdarcs | ||
| fetchfile | ||
| fetchgit | ||
| fetchgitrevision | ||
| fetchhg | ||
| fetchmtn | ||
| fetchsvn | ||
| fetchsvnrevision | ||
| fetchsvnssh | ||
| fetchurl | ||
| gcc-cross-wrapper | ||
| gcc-wrapper | ||
| kdewrapper | ||
| kernel | ||
| make-desktopitem | ||
| make-startupitem | ||
| make-symlinks | ||
| mono-dll-fixer | ||
| native-darwin-cctools-wrapper | ||
| nuke-references | ||
| release | ||
| setup-hooks | ||
| src-only | ||
| substitute | ||
| upstream-updater | ||
| vm | ||
| vsenv | ||
| replace-dependency.nix | ||
| source-from-head-fun.nix | ||
| trivial-builders.nix | ||