I was reading a DMP file to investigate customer issue where they have been having high CPU issues after latest upgrade. I read the dmp with windbg then vs.net analyze and both times I saw CLR GC(garbage collection and BGC) was eating up all the CPU and I must say VS.NET analyze is really nice, it shows who is eating up the CPU very easily, only problem it may crash sometimes, the dmp file size was around 9GB that maybe the reason I do not know. ...

In short I am explaining why we should use ./mvnw -Pnative native:compile and what error comes otherwise and why. I was preparing this answer. And I was having problem with the class not found errors while building because I was using this command ./mvnw native:compile ... Error: Please specify class (or <module>/<mainclass>) containing the main entry point method. (see --help) [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 3.448 s [INFO] Finished at: 2024-09-01T21:24:32+01:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.graalvm.buildtools:native-maven-plugin:0.10.2:compile (default-cli) on project env-variables: Execution of C:\sdkman\candidates\java\21.0.2-graal\bin\native-image.cmd @target\tmp\native-image-2373453772169200185.args returned non-zero result -> [Help 1] [ERROR] Then remembered the profile thing and finally get rid of this error, used below command ...

I used eclipse 10 years and moved to IntelliJ in 2017 since then no turning back, a true Java IDE, perfect refactoring also any editing capabilities, and in 2024 I moved to Redgate Monitor and C# after 18 years of Java I was scared but thanks to JetBrains Rider, when I open the Rider it asked me what shortcut set do I choose, and there was IntelliJ option, I chose it and jumped into the code and adoption time was incredible, in days I understand how is the structure (over 180 projects under multiple solution and thousands of classes/files) and started contributing the project. ...

Jetbrains fleet is a new editor, it is kind of vscode competitor, and little bit faster then other IDEA and VScode so I wanted to ahve it in the context menu. @echo off setlocal enabledelayedexpansion :: Set the path to your Fleet executable using %USERPROFILE% set "FLEET_PATH=%USERPROFILE%\AppData\Local\Programs\Fleet\Fleet.exe" :: Check if running with admin privileges net session >nul 2>&1 if %errorLevel% neq 0 ( echo This script requires administrator privileges. echo Please run it as an administrator. pause exit /b 1 ) :: Add Fleet to context menu reg add "HKEY_CLASSES_ROOT\Directory\Background\shell\Fleet" /ve /d "Open with Fleet" /f reg add "HKEY_CLASSES_ROOT\Directory\Background\shell\Fleet\command" /ve /d "\"%FLEET_PATH%\" \"%%V\"" /f reg add "HKEY_CLASSES_ROOT\Directory\Background\shell\Fleet" /v "Icon" /d "%FLEET_PATH%" /f echo Fleet has been added to the context menu. echo Please restart File Explorer or your PC for changes to take effect. pause looks like below ...

Jpackage, a powerful tool introduced in Java 14. In this blog post, I’ll explore how to use jpackage to create installers for different operating systems, with a focus on creating an MSI installer for Windows. What is jpackage? jpackage is a packaging tool that comes bundled with the Java Development Kit (JDK) since version 14. It allows developers to package Java applications into platform-specific packages that can be easily distributed and installed. It contains the JRE in the generated package and one trigger executable for specified platform. jpackage supports creating various types of installers, including: ...