Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| 09e3afc6 | 2025-07-31 15:45:42 | switch jBCrypt to MODJAVA_VER=11+ | ||
| 950fd315 | 2023-09-19 22:02:32 | use SITES | ||
| b6966d2e | 2022-03-07 21:45:09 | GC a few more RCS ids in my ports | ||
| a98e0e66 | 2022-03-07 21:36:41 | remove rcs IDs in ports that I maintain | ||
| f9d899e6 | 2021-05-19 01:50:29 | Bump revision on all 1.8+ ports since now they will build with jdk 1.8 on aarch64 and their run depends will also change. okay ian@ | ||
| 7823f29c | 2021-01-22 13:42:09 | accept $2b bcrypt hashes; jBCrypt never had the 256-char bug use https HOMEPAGE/MASTER_SITES while there | ||
| 6cc97792 | 2020-07-11 22:54:35 | switch my maintainer email addresses to my own domain | ||
| 7705a5ad | 2019-06-11 00:38:33 | Revision bump all java ports for the jre package removal and java.port.mk changes. | ||
| 9c6e9626 | 2019-06-03 16:06:50 | s/PERMIT_PACKAGE_CDROM/PERMIT_PACKAGE/ and some light whitespace tidying in ports which I maintain | ||
| 828f08b0 | 2019-03-24 22:24:12 | sweep all java ports with a couple of adjustments to build/dependency environment, which will reduce complexity in java.port.mk when jdk 11 is added. direction agreed with kurt@. - switch all MODJAVA_VER to at least 1.8 (we don't currently have any version earlier than this anyway). - drop MODJAVA_JRERUN, the separate jre package will be going away with jdk 11. - bump changed ports |