about summary refs log tree commit diff
path: root/pkgs/applications/networking/jmeter
AgeCommit message (Collapse)AuthorFilesLines
2024-01-08jmeter: 5.6.2 -> 5.6.3R. Ryantm1-2/+2
2023-08-10jmeter: 5.6 -> 5.6.2R. Ryantm1-2/+2
2023-06-24jmeter: 5.5 -> 5.6Bryan A. S1-2/+2
2023-01-21treewide: switch to nativeCheckInputsGuillaume Girol1-1/+1
checkInputs used to be added to nativeBuildInputs. Now we have nativeCheckInputs to do that instead. Doing this treewide change allows to keep hashes identical to before the introduction of nativeCheckInputs.
2022-06-17jmeter: 5.4.3 -> 5.5Bryan A. S1-2/+2
2021-12-25jmeter: 5.4.2 -> 5.4.3Bryan A. S1-2/+2
Update log4j to 2.17.0 (fix CVE-2021-45105)
2021-12-17jmeter: 5.4.1 -> 5.4.2Bryan A. S1-2/+2
fix for CVE-2021-44228
2021-01-30jmeter: 5.4 -> 5.4.1R. RyanTM1-2/+2
2021-01-18jmeter: 5.1.1 > 5.4Bryan A. S1-5/+5
Update Jmeter to the latest version, also add myself as a maintainer I have been using the package for 5 months daily, at the moment I am aware of 3 bugs. 1. Jmeter fails to save test plan in /nix/store (by default it saves it where Jmeter was installed). 2. The test fails to run on the latest version complaining about some missing libraries, for example log4j. 3. Jmeter fails to generate the report from a JTL file, for some reason it is not copying the needed files sometimes it fails without any log or error. The rest works perfectly, but I still plan to fix it at somepoint, as I only use it for development, I didn't find any other bugs, and in the case of the report generator it is possible to generate it during the test run (in my case, the test is run on a non-NIXOS machine) or in a container. Also add why tests are disabled. Signed-off-by: Bryan A. S <bryanasdev000@gmail.com>
2021-01-11treewide: with stdenv.lib; in meta -> with lib;Profpatsch1-2/+2
Part of: https://github.com/NixOS/nixpkgs/issues/108938 meta = with stdenv.lib; is a widely used pattern. We want to slowly remove the `stdenv.lib` indirection and encourage people to use `lib` directly. Thus let’s start with the meta field. This used a rewriting script to mostly automatically replace all occurances of this pattern, and add the `lib` argument to the package header if it doesn’t exist yet. The script in its current form is available at https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
2019-08-15treewide: name -> pname (easy cases) (#66585)volth1-2/+2
treewide replacement of stdenv.mkDerivation rec { name = "*-${version}"; version = "*"; to pname
2019-07-03Remove me (garbas) as maintainer since I don't have much time to maintain ↵Rok Garbas1-1/+1
anything
2019-05-01jmeter: 5.1 -> 5.1.1R. RyanTM1-2/+2
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/jmeter/versions
2019-04-07jmeter: 4.0 -> 5.1 (#57257)R. RyanTM1-2/+2
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/jmeter/versions
2018-06-28treewide: http -> https sources (#42676)Silvan Mosberger1-1/+1
* treewide: http -> https sources This updates the source urls of all top-level packages from http to https where possible. * buildtorrent: fix url and tab -> spaces
2018-02-28jmeter: 3.3 -> 4.0 (#35655)Markus Hauck1-11/+39
* jmeter: 3.3 -> 4.0
2017-12-26jmeter: 2.11 -> 3.3 and fix java command not foundAlexandre Peyroux1-3/+7
2016-08-02treewide: Add lots of meta.platformsTuomas Tynkkynen1-0/+1
Build-tested on x86_64 Linux & Mac.
2014-11-18jmeter: fix download URLLongrin Wischnewski1-1/+1
2014-08-24Fix many package descriptionsBjørn Forsman1-1/+1
(My OCD kicked in today...) Remove repeated package names, capitalize first word, remove trailing periods and move overlong descriptions to longDescription. I also simplified some descriptions as well, when they were particularly long or technical, often based on Arch Linux' package descriptions. I've tried to stay away from generated expressions (and I think I succeeded). Some specifics worth mentioning: * cron, has "Vixie Cron" in its description. The "Vixie" part is not mentioned anywhere else. I kept it in a parenthesis at the end of the description. * ctags description started with "Exuberant Ctags ...", and the "exuberant" part is not mentioned elsewhere. Kept it in a parenthesis at the end of description. * nix has the description "The Nix Deployment System". Since that doesn't really say much what it is/does (especially after removing the package name!), I changed that to "Powerful package manager that makes package management reliable and reproducible" (borrowed from nixos.org). * Tons of "GNU Foo, Foo is a [the important bits]" descriptions is changed to just [the important bits]. If the package name doesn't contain GNU I don't think it's needed to say it in the description either.
2014-06-01jsmeter: update to 2.11Rok Garbas1-2/+2
2013-11-23jmeter: update to 2.10Rok Garbas1-3/+3
2013-10-07adding jmeterRok Garbas1-0/+27