Java - Revision history

Frontear: it is important that this path is written like this because this extension relies on other directories besides `bin/` to configure the jdt language server. without this path, the language server erroneously fails and displays confusing errors.

2026-01-23T23:39:40Z

it is important that this path is written like this because this extension relies on other directories besides `bin/` to configure the jdt language server. without this path, the language server erroneously fails and displays confusing errors.

← Older revision		Revision as of 23:39, 23 January 2026
Line 50:		Line 50:

	programs.vscode.userSettings = {		programs.vscode.userSettings = {
	"java.jdt.ls.java.home" = "${pkgs.jdk17}";		"java.jdt.ls.java.home" = "${pkgs.jdk17}/lib/openjdk";
	};		};
	</syntaxhighlight>Note that this will still result in the extension downloading its own JRE, it just will not be used.		</syntaxhighlight>Note that this will still result in the extension downloading its own JRE, it just will not be used.

Makefu: update package sample links

2025-12-24T21:43:08Z

update package sample links

← Older revision		Revision as of 21:43, 24 December 2025
Line 181:		Line 181:
	==== Ivy ====		==== Ivy ====

	[https://ant.apache.org/ivy/ Ivy] is a package manager for Ant, not to be confused with [https://github.com/NixOS/nixpkgs/blob/master/pkgs/~~development~~/~~interpreters~~/ivy/~~default~~.nix ivy] - an APL-like calculator		[https://ant.apache.org/ivy/ Ivy] is a package manager for Ant, not to be confused with [https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/iv/ivy/package.nix ivy] - an APL-like calculator

	To fetch ivy sources manually, see for example [https://github.com/NixOS/nixpkgs/blob/master/pkgs/~~applications~~/~~editors~~/jedit pkgs/applications/editors/jedit]		To fetch ivy sources manually, see for example [https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/je/jedit/package.nix pkgs/applications/editors/jedit]

	To fetch ivy sources in a fixed-output-derivation, see for example [https://github.com/milahu/nur-packages/blob/master/pkgs/yacy/yacy.nix yacy.nix]		To fetch ivy sources in a fixed-output-derivation, see for example [https://github.com/milahu/nur-packages/blob/master/pkgs/yacy/yacy.nix yacy.nix]

Badcold: /* jdk11 */ alternatives to overriding cacert for jdk11+

2025-03-23T16:06:00Z

jdk11: alternatives to overriding cacert for jdk11+

← Older revision		Revision as of 16:06, 23 March 2025
Line 151:		Line 151:
	=== jdk11 ===		=== jdk11 ===

	JDK11 does not provide the cacert overridable and therefore it is not possible to use the same technique to override the truststore.		JDK11 does not provide the cacert overridable and therefore it is not possible to use the same technique to override the truststore.

			As an alternative solution you can either set an environment variable, <code>JAVAX_NET_SSL_TRUSTSTORE</code>, or pass an argument to your program, <code>-Djavax.net.ssl.trustStore</code>, with the location of your cacert. See [https://discourse.nixos.org/t/custom-ssl-certificates-for-jdk/18297/9 discussion].

	== Building and Packaging ==		== Building and Packaging ==

Klinger: Category:Applications removed

2025-03-20T14:54:26Z

Category:Applications removed

← Older revision		Revision as of 14:54, 20 March 2025
Line 203:		Line 203:
	{{Nixpkgs manual\|sec-language-java}}<br /><br /><br /><br /><br />{{Wikipedia\|Java_(programming_language)}}		{{Nixpkgs manual\|sec-language-java}}<br /><br /><br /><br /><br />{{Wikipedia\|Java_(programming_language)}}

	~~[[Category:Applications]]~~
	[[Category:Languages]]		[[Category:Languages]]

Kvtb: JavaFX/Webkit

2024-12-10T19:35:09Z

JavaFX/Webkit

@@ Line 185: / Line 185: @@
 To fetch ivy sources in a fixed-output-derivation, see for example [https://github.com/milahu/nur-packages/blob/master/pkgs/yacy/yacy.nix yacy.nix]
 == Further reading ==
 {{Nixpkgs manual|sec-language-java}}<br /><br /><br /><br /><br />{{Wikipedia|Java_(programming_language)}}

Fidgetingbits: Minor formatting/wording tweaks

2024-10-24T15:32:40Z

Minor formatting/wording tweaks

← Older revision		Revision as of 15:32, 24 October 2024
Line 9:		Line 9:
	== JDK options ==		== JDK options ==

	Your default choice should probably be to install <code>jdk</code>, which is an alias the latest LTS. If you're in a server environment, go for <code>jdk21_headless</code>. Java 21 is the currently-maintained LTS version of OpenJDK as of April 2024.		Your default choice should probably be to install <code>jdk</code>, which is an alias to the latest [https://en.wikipedia.org/wiki/Long-term_support LTS]. If you're in a server environment, go for <code>jdk21_headless</code>. Java 21 is the currently-maintained LTS version of OpenJDK as of April 2024.

	As you might expect, though, many flavors of Java are available in NixOS.		As you might expect, though, many flavors of Java are available in NixOS.
Line 24:		Line 24:

	== VSCode + Language Support for Java (TM) by Red Hat extension ==		== VSCode + Language Support for Java (TM) by Red Hat extension ==
	Unfortunately the extension contains and uses a version of the JRE which makes use of dynamically loaded libraries, which nix cannot accomodate out-of-the-box. Fortunately there's a simple solution in the use of [https://github.com/Mic92/nix-ld nix-ld]. Here's a simple flake.nix to get you started (I'll focus on the devShell part for brevity):		Unfortunately the extension contains and uses a version of the JRE which makes use of dynamically loaded libraries, which nix cannot accomodate out-of-the-box. Fortunately there's a simple solution in the use of [https://github.com/Mic92/nix-ld nix-ld]. Here's a simple <code>flake.nix</code> snippet to get you started (I'll focus on the <code>devShell</code> part for brevity):

	<syntaxhighlight lang="nix" line highlight="6,10" copy>		<syntaxhighlight lang="nix" line highlight="6,10" copy>
			# flake.nix
	devShell = pkgs.mkShell {		devShell = pkgs.mkShell {
	buildInputs = [		buildInputs = [
Line 41:		Line 42:
	</syntaxhighlight>		</syntaxhighlight>

	The important lines above are the two starting with <code>NIX_LD...</code>. They will let nix-ld wrap the required, dynamically loaded libraries so that they are found when building the devShell.		The important lines above are the two starting with <code>NIX_LD...</code>. They will let nix-ld wrap the required, dynamically loaded libraries so that they are found when building the <code>devShell</code>.

	Another solution is to use the <code>[https://github.com/redhat-developer/vscode-java?tab=readme-ov-file#supported-vs-code-settings java.jdt.ls.java.home]</code> VSCode setting to point to a nix-built Java 17. For example, using home-manager's settings: <syntaxhighlight lang="nix">		Another solution is to use the <code>[https://github.com/redhat-developer/vscode-java?tab=readme-ov-file#supported-vs-code-settings java.jdt.ls.java.home]</code> VSCode setting to point to a nix-built Java 17. For example, using home-manager's settings: <syntaxhighlight lang="nix">
Line 54:		Line 55:

	== Using Oracle JDK instead of Open JDK ==		== Using Oracle JDK instead of Open JDK ==
	Almost all Java packages in nixpkgs use Open JDK in form of a '''jre''' dependency. If you use Oracle JDK and also want other applications to use it, you can simply tweak your <code>.nixpkgs/config.nix</code> so that your desired application uses Oracles JDK or JRE.		Almost all Java packages in nixpkgs use Open JDK in form of a '''jre''' dependency. If you use Oracle JDK and also want other applications to use it, you can simply tweak your <code>nixpkgs/config.nix</code> so that your desired application uses Oracles JDK or JRE.

	Example with UMLet with JRE		Example with UMLet with JRE
Line 69:		Line 70:

	To install the Oracle JRE system-wide, you need to explicitly accept the license in addition to allowing unfree modules:		To install the Oracle JRE system-wide, you need to explicitly accept the license in addition to allowing unfree modules:

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	# /etc/nixos/configuration.nix		# /etc/nixos/configuration.nix
Line 77:		Line 79:
	</syntaxhighlight>		</syntaxhighlight>

	Working with `requireFile` (manual downloading the tarballs and manual adding in to the nix store) might be annoying and nixops-unfriendly, so it can be overridden in overlays		Working with <code>requireFile</code> (manual downloading the tarballs and manual adding in to the nix store) might be annoying and nixops-unfriendly, so it can be overridden in overlays

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
Line 106:		Line 108:
	== Better font rendering==		== Better font rendering==

	By default java does not enable ~~antialiasing~~ for font rendering. By exporting environment variables, this can be fixed:		By default java does not enable anti-aliasing for font rendering. By exporting environment variables, this can be fixed:

	<syntaxhighlight lang="console">		<syntaxhighlight lang="console">
Line 115:		Line 117:

	== Overriding java jks Certificate Store ==		== Overriding java jks Certificate Store ==

	Overriding the java certificate store may be required for adding your own Root certificates in case your company uses an internal PKI or the company utilizes an intercepting proxy.		Overriding the java certificate store may be required for adding your own Root certificates in case your company uses an internal PKI or the company utilizes an intercepting proxy.

	=== jdk8 ===		=== jdk8 ===

	Overriding the jdk8 certificate store is possible by overriding the '''cacert''' parameter of the package:		Overriding the jdk8 certificate store is possible by overriding the '''cacert''' parameter of the package:

Line 145:		Line 150:

	=== jdk11 ===		=== jdk11 ===

	JDK11 does not provide the cacert overridable and therefore it is not possible to use the same technique to override the truststore.		JDK11 does not provide the cacert overridable and therefore it is not possible to use the same technique to override the truststore.

Fidgetingbits: /* VSCode + Language Support for Java (TM) by Red Hat extension */ minor wording change

2024-10-24T15:08:26Z

VSCode + Language Support for Java (TM) by Red Hat extension: minor wording change

← Older revision		Revision as of 15:08, 24 October 2024
Line 24:		Line 24:

	== VSCode + Language Support for Java (TM) by Red Hat extension ==		== VSCode + Language Support for Java (TM) by Red Hat extension ==
	Unfortunately the extension contains and uses a version of the JRE which makes use of dynamically loaded libraries, which nix cannot accomodate out-of-the-box. Fortunately there's a simple solution in the use of [https://github.com/Mic92/nix-ld nix-ld]. Here's a simple flake.nix to get you started (I'll focus on the devShell part for brevity):<syntaxhighlight lang="nix" line highlight="6,10">		Unfortunately the extension contains and uses a version of the JRE which makes use of dynamically loaded libraries, which nix cannot accomodate out-of-the-box. Fortunately there's a simple solution in the use of [https://github.com/Mic92/nix-ld nix-ld]. Here's a simple flake.nix to get you started (I'll focus on the devShell part for brevity):

			<syntaxhighlight lang="nix" line highlight="6,10" copy>
	devShell = pkgs.mkShell {		devShell = pkgs.mkShell {
	buildInputs = [		buildInputs = [
Line 37:		Line 39:
	# ^--- when using direnv, this line will require the 'use flake --impure' option.		# ^--- when using direnv, this line will require the 'use flake --impure' option.
	};		};
	</syntaxhighlight>The important lines are the two ~~lines~~ starting with "NIX_LD...". They will let nix-ld wrap the required, dynamically loaded libraries so that they are found when building the devShell.		</syntaxhighlight>

			The important lines above are the two starting with <code>NIX_LD...</code>. They will let nix-ld wrap the required, dynamically loaded libraries so that they are found when building the devShell.

	Another solution is to use the <code>[https://github.com/redhat-developer/vscode-java?tab=readme-ov-file#supported-vs-code-settings java.jdt.ls.java.home]</code> VSCode setting to point to a nix-built Java 17. For example, using home-manager's settings: <syntaxhighlight lang="nix">		Another solution is to use the <code>[https://github.com/redhat-developer/vscode-java?tab=readme-ov-file#supported-vs-code-settings java.jdt.ls.java.home]</code> VSCode setting to point to a nix-built Java 17. For example, using home-manager's settings: <syntaxhighlight lang="nix">

Fidgetingbits: /* VSCode + Language Support for Java (TM) by Red Hat extension */ add highlights to the lines being described

2024-10-24T15:04:18Z

VSCode + Language Support for Java (TM) by Red Hat extension: add highlights to the lines being described

← Older revision		Revision as of 15:04, 24 October 2024
Line 24:		Line 24:

	== VSCode + Language Support for Java (TM) by Red Hat extension ==		== VSCode + Language Support for Java (TM) by Red Hat extension ==
	Unfortunately the extension contains and uses a version of the JRE which makes use of dynamically loaded libraries, which nix cannot accomodate out-of-the-box. Fortunately there's a simple solution in the use of [https://github.com/Mic92/nix-ld nix-ld]. Here's a simple flake.nix to get you started (I'll focus on the devShell part for brevity):<syntaxhighlight lang="nix">		Unfortunately the extension contains and uses a version of the JRE which makes use of dynamically loaded libraries, which nix cannot accomodate out-of-the-box. Fortunately there's a simple solution in the use of [https://github.com/Mic92/nix-ld nix-ld]. Here's a simple flake.nix to get you started (I'll focus on the devShell part for brevity):<syntaxhighlight lang="nix" line highlight="6,10">
	devShell = pkgs.mkShell {		devShell = pkgs.mkShell {
	buildInputs = [		buildInputs = [

Miniluz: /* VSCode + Language Support for Java (TM) by Red Hat extension */ Add alternate solution for using Language Support for Java

2024-10-14T15:32:15Z

VSCode + Language Support for Java (TM) by Red Hat extension: Add alternate solution for using Language Support for Java

← Older revision		Revision as of 15:32, 14 October 2024
Line 24:		Line 24:

	== VSCode + Language Support for Java (TM) by Red Hat extension ==		== VSCode + Language Support for Java (TM) by Red Hat extension ==
	Unfortunately the extension makes use of dynamically loaded libraries which nix cannot accomodate out-of-the-box. Fortunately there's a simple solution in the use of [https://github.com/Mic92/nix-ld nix-ld]. Here's a simple flake.nix to get you started (I'll focus on the devShell part for brevity):<syntaxhighlight lang="nix">		Unfortunately the extension contains and uses a version of the JRE which makes use of dynamically loaded libraries, which nix cannot accomodate out-of-the-box. Fortunately there's a simple solution in the use of [https://github.com/Mic92/nix-ld nix-ld]. Here's a simple flake.nix to get you started (I'll focus on the devShell part for brevity):<syntaxhighlight lang="nix">
	devShell = pkgs.mkShell {		devShell = pkgs.mkShell {
	buildInputs = [		buildInputs = [
Line 38:		Line 38:
	};		};
	</syntaxhighlight>The important lines are the two lines starting with "NIX_LD...". They will let nix-ld wrap the required, dynamically loaded libraries so that they are found when building the devShell.		</syntaxhighlight>The important lines are the two lines starting with "NIX_LD...". They will let nix-ld wrap the required, dynamically loaded libraries so that they are found when building the devShell.

			Another solution is to use the <code>[https://github.com/redhat-developer/vscode-java?tab=readme-ov-file#supported-vs-code-settings java.jdt.ls.java.home]</code> VSCode setting to point to a nix-built Java 17. For example, using home-manager's settings: <syntaxhighlight lang="nix">
			programs.vscode.enable = true;

			programs.vscode.extensions = [ pkgs.vscode-extensions.redhat.java ];

			programs.vscode.userSettings = {
			"java.jdt.ls.java.home" = "${pkgs.jdk17}";
			};
			</syntaxhighlight>Note that this will still result in the extension downloading its own JRE, it just will not be used.

	== Using Oracle JDK instead of Open JDK ==		== Using Oracle JDK instead of Open JDK ==

Phanirithvij: buildmavenpackage and fix buildmaven link

2024-09-15T06:29:43Z

buildmavenpackage and fix buildmaven link

← Older revision		Revision as of 06:29, 15 September 2024
Line 143:		Line 143:
	<pre>mvn verify</pre>		<pre>mvn verify</pre>

	[https://github.com/fzakaria/mvn2nix mvn2nix] ~~and~~ [https://~~github~~.~~com~~/~~NixOS~~/nixpkgs/~~blob~~/~~master/pkgs/build~~-~~support/build-maven.nix buildMaven~~] can be used to build Maven projects with Nix		[https://github.com/fzakaria/mvn2nix mvn2nix], [https://nixos.org/manual/nixpkgs/stable/#maven-buildmavenpackage buildMavenPackage] (recommended) can be used to build Maven projects with Nix

	See also: [https://fzakaria.com/2020/07/20/packaging-a-maven-application-with-nix.html Packaging a Maven application with Nix]		See also: [https://fzakaria.com/2020/07/20/packaging-a-maven-application-with-nix.html Packaging a Maven application with Nix] and [https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/ma/maven/build-maven-package.nix buildMavenPackage source]

	=== Ant ===		=== Ant ===