IDE Eval Resetter
IDE Eval Resetter is a plugin that can reset your IDE evaluation information. This allows you to extend the evaluation period for JetBrains IDEs.
No cracks, no sketchy binaries. Just clean eval resets.
Usage:
- Click
HelporGet HelpβEval Resetmenu - Click
ResetβYesbutton - Restart your IDE
- You will have another evaluation period
For more information, visit the project repository.
Table of contents
- Installation
- Usage
- Project structure
- Getting started
- Gradle configuration
- Plugin configuration file
- Build commands
- Testing
- Continuous integration
- Contributing
Installation
Manual Installation
- Download the latest plugin ZIP from GitHub Releases
- In your IDE, go to
Settings/PreferencesβPlugins - Click the gear icon and select
Install Plugin from Disk... - Select the downloaded ZIP file
Usage
- Click
HelporGet HelpβEval Resetmenu - Click
ResetβYesbutton - Restart your IDE
- You now have another 30 days evaluation time
Project structure
This IntelliJ Platform Plugin uses modern Kotlin development practices and follows the standard plugin architecture:
.
βββ .github/ GitHub Actions workflows
βββ .run/ Predefined Run/Debug Configurations
βββ build/ Output build directory
βββ gradle/
β βββ wrapper/ Gradle Wrapper
β βββ libs.versions.toml Gradle version catalog
βββ scripts/ Platform-specific reset scripts
βββ src/ Plugin sources
β βββ main/
β β βββ kotlin/ Kotlin production sources
β β β βββ dev/samhoque/intellij/ier/
β β β βββ action/ User actions (ResetAction, RestartAction)
β β β βββ common/ Core business logic and services
β β β βββ listeners/ Event listeners
β β β βββ ui/ User interface components
β β β βββ util/ Utility classes
β β βββ resources/ Resources - plugin.xml, icons, messages
β βββ test/ Test sources
βββ build.gradle.kts Gradle configuration
βββ CHANGELOG.md Full change history
βββ CLAUDE.md Development instructions
βββ gradle.properties Gradle configuration properties
βββ qodana.yml Qodana configuration file
βββ README.md This file
Getting started
This project uses Kotlin and the IntelliJ Platform Plugin development framework. To get started:
- Clone the repository
- Open the project in IntelliJ IDEA
- Ensure you have Java 17 configured in your Project Structure settings
- Use the predefined Run/Debug configurations to run or test the plugin
Gradle configuration
The project uses Gradle with the IntelliJ Platform Gradle Plugin for development and build automation.
Key features:
- Kotlin DSL configuration with type-safe build scripts
- Version catalog for centralized dependency management
- IntelliJ Platform Plugin 2.6.0 for modern plugin development
- Kotlin 2.1.20 following JetBrains standards
- Java 17 toolchain requirement
- Gradle 8.13 with configuration cache optimization
Gradle properties
The project configuration in gradle.properties includes:
| Property | Description |
|---|---|
pluginGroup |
Package namespace: dev.samhoque.intellij.ier |
pluginName |
Plugin display name |
pluginVersion |
Current version in SemVer format |
platformType |
IDE type (IU = IntelliJ IDEA Ultimate) |
platformVersion |
Target IntelliJ Platform version |
pluginSinceBuild |
Minimum supported IDE build |
pluginUntilBuild |
Maximum supported IDE build |
Plugin configuration file
The plugin.xml file defines:
- Plugin metadata and vendor information
- IDE compatibility ranges
- Action registrations and menu integrations
- Extension points and services
- Resource bundles and icons
Build commands
Important: This project requires Java 17. If you have a newer Java version, specify the path:
With Java 17 as default ./gradlew buildPlugin # With newer Java version (e.g., Java 24) JAVA_HOME=/path/to/java17 ./gradlew buildPlugin
Available commands:
./gradlew buildPlugin- Build the plugin (creates ZIP inbuild/distributions/)./gradlew test- Run unit tests./gradlew clean- Clean build artifacts./gradlew runIde- Run IDE with plugin for testing
Testing
The project includes JUnit 4.13.2 for testing infrastructure. While no tests are currently implemented, the framework is configured and ready for test development.
Run tests with:
./gradlew test
Continuous integration
GitHub Actions workflows handle:
- Build: Triggered on push/PR, runs verification and creates draft releases
- Release: Publishes to JetBrains Marketplace when releases are created
- Quality: Qodana code quality analysis integration
Contributing
- Fork the repository
- Create a feature branch
- Make your changes following the existing code style
- Build and test your changes:
./gradlew buildPlugin test - Submit a pull request
For development guidelines, see CLAUDE.md.

!