Nixpkgs: needs packaging: Eclipse Memory Analyzer

[coretemp]

Issue description

Eclipse Memory Analyzer is missing from nixpkgs.
https://www.eclipse.org/mat/downloads.php

Technical details

• system: "x86_64-linux"
• host os: Linux 4.14.48, NixOS, 18.03.git.411cc55 (Impala)
• multi-user?: yes
• sandbox: no
• version: nix-env (Nix) 2.0.4
• nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

[phdoerfler]

This is hands down the best free (dunno about paid) software for analyzing java heap dumps. By far!
I would love to see this in NixOS.
I'd file a PR myself but I'm afraid my nixfu is a bit rusty and I would probably bind more resources because of me needing help than if someone experienced would do it.

[ktor]

I do have a local config that almost works. Reviewing some reports inside Eclipse still does not work due to gtk2 but with gtk3 it doesn't work at all. I'm using following FHS expression for that:

let
  nixpkgs = import <nixpkgs> {};
  previous = import <previous> { config = nixpkgs.config; };
  unstable = import <unstable> { config = nixpkgs.config; };
in nixpkgs.buildFHSUserEnv {
   name = "fhs";
   targetPkgs = pkgs: [];
   multiPkgs = pkgs: [
     pkgs.fontconfig
     pkgs.freetype
     pkgs.glib
     pkgs.gsettings-desktop-schemas
     pkgs.gtk2-x11
     pkgs.zulu8
     pkgs.xorg.libXi
     pkgs.xorg.libX11
     pkgs.xorg.libXtst
     pkgs.xorg.libXrender
     pkgs.xorg.libXxf86vm
     pkgs.zlib
     unstable.pkgs.webkitgtk
   ];
   runScript = "bash";
}

this should be more or less trasferrable to a package. I'll try to prepare this during the weekend. Code review process will hopefully help to polish the setup.

[ktor]

Good news @phdoerfler, I have a working package! Thank you for poking on this issue!!

My config unfortunately wasn't as transferable as I've expected but I was able to reuse most of the eclipse builder expression https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/editors/eclipse/build-eclipse.nix. It was even possible to get around the gtk3 problem just by using jdk11. The suggestion that jdk may be a problem came from https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736#c61 comment.

I'll be glad if you test this.

[phdoerfler]

Fantastic @ktor, thank you so much! I'll be sure to give this a try in the next days. I actually the memory analyzer then so this is impeccable timing :)

[phdoerfler]

I've given it a try and it works great! Definitely beats running it in a VM ;)
Thanks again @ktor for taking the time to get this to work and @coretemp for filing the PR in the first place.