The frontend tool for identifying (un-)used JAR libraries.
- Find unused JAR libraries in your project
- Identify multiple versions of same libraries of the same project
Column | Meaning |
---|---|
In Use |
Indicates whether the JAR library is loaded by the Java Runtime or not. If not, this would be a candidate for removal. |
Overloaded |
- Warn (Orange) - An identical JAR was found multiple times in one of the specified directories with identical version - Stop (red) - An identical JAR was found several times in one of the specified directories with different versions |
Elapsed Time |
The time in milliseconds after the Java Runtime Environment was started that the JAR file was loaded. |
Filename |
Name of the JAR file |
POM |
Checked if at least one POM properties file was found in the JAR |
File |
Full qualified path of the JAR file |
# clone the project
git clone https://github.com/elomagic/elo-agent.git
# enter the project directory
cd elo-agent
# install dependency
npm install
# develop
npm run dev
Familiar React application structure, just with electron
folder on the top 😉
Files in this folder will be separated from your React application and built into dist-electron
├── electron Electron-related code
│ ├── main Main-process source code
│ └── preload Preload-scripts source code
│
├── release Generated after production build, contains executables
│ └── {version}
│ ├── {os}-{os_arch} Contains unpacked application executable
│ └── {app_name}_{version}.{ext} Installer for the application
│
├── public Static assets
└── src Renderer source code, your React application
Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.
Versioning follows the semantic of Semantic Versioning 2.0.0
The Elo Agent tool is distributed under Apache License, Version 2.0
Donations will ensure the following:
- 🔨 Long term maintenance of the project
- 🛣 Progress on the roadmap
- 🐛 Quick responses to bug reports and help requests