nixpkgs

mirrors/nixpkgs

Fork 1

mirror of https://github.com/NixOS/nixpkgs.git synced 2024-12-25 03:17:13 +00:00

Commit graph

Author	SHA1	Message	Date
Eelco Dolstra	e3f7dbbac8	Cleanup: Use += to append to envHooks	2014-08-09 12:47:05 +02:00
Eelco Dolstra	5d6259a973	Add a setup hook that automatically sets up $CLASSPATH 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.)	2014-01-06 14:36:14 +01:00

Author

SHA1

Message

Date

Eelco Dolstra

e3f7dbbac8

Cleanup: Use += to append to envHooks

2014-08-09 12:47:05 +02:00

Eelco Dolstra

5d6259a973

Add a setup hook that automatically sets up $CLASSPATH

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.)

2014-01-06 14:36:14 +01:00

2 commits