summaryrefslogtreecommitdiff
path: root/mk/java-env.mk
AgeCommit message (Collapse)AuthorFilesLines
2005-03-19Let this file be included even if JAVA_WRAPPERS is empty; this was possiblejmmv1-14/+14
before, but after the introduction of alternatives, a regression appeared. This is useful for packages that install files inside ${PREFIX}/java so that the directory is automatically removed when empty. Problem exposed by sablevm-classpath as described in PR pkg/29643 by Antoine Reilles.
2005-01-30Convert the Java related packages to use the alternatives system. To dojmmv1-1/+8
this, we only need some simple logic in java-env.mk to automatically generate an ALTERNATIVES file for us. There are two exceptions, though: fastjar and jikes (pointed out by tv@), which do not use this file; they have to be handled manually. Bump PKGREVISION for all affected packages. While doing this, remove the java-wrapper package, obsoleted by the new functionality provided by pkg_alternatives.
2004-05-23Lets be pkgviews friendly: create the bin directory when installing wrappers.jmmv1-1/+5
2004-05-23Let a package specify which is the real binary for each wrapper (by settingjmmv1-2/+4
JAVA_WRAPPER_BIN.<wrapper-name>), in case it differs from the default. For example, sablevm does not install a 'java' program with that name, so adding 'java' to JAVA_WRAPPERS couldn't DTRT.
2004-05-22Initial addition.jmmv1-0/+74
This file provides a framework to easily create wrappers to run Java environments (either compilers or virtual machines) installed under ${PREFIX}/java/<implementation>. These wrappers hide the complexity of having to modify the path, unlimit resources or to set a correct CLASSPATH for the program to run.