- Open Project: Open the root
SimplifyLearningdirectory in IntelliJ - Gradle Import: IntelliJ should automatically detect and import the
algorithms-javaGradle module - SDK Setup: Ensure Java 21 is configured as project SDK
- Refresh Project: If you see "Directory does not contain a Gradle build" error:
- Gradle Tool Window → Click + → Link Gradle Project
- Select
algorithms-javadirectory (NOT the root directory) - Click OK
- SimplifyLearning (root): Container project with build scripts and documentation
- algorithms-java: Java implementations with
gradlebuild system - algorithms-js: JavaScript implementations with
npmscripts
cd algorithms-java
./gradlew build- Fast Build:
./gradlew dev- Runs tests with coverage printing (no verification failures) - Quick Compile:
./gradlew quick- Compile only, no tests - Full Build:
./gradlew build- Complete build with all reports
cd algorithms-js
npm start # Starts Python dev server on port 8080- JavaScript Dev Server: Runs
npm startfrom IntelliJ
./build.sh # Build both modules
./build.sh java # Build Java only
./build.sh js # Build JavaScript onlycd algorithms-java
./gradlew dev # Fast development build
./gradlew quick # Compile only
./gradlew test # Tests only
./gradlew build # Full build with reportscd algorithms-js
npm start # Start dev server
npm run dev # Same as start
npm run clean # Kill servers on port 8080"Directory does not contain a Gradle build" Error:
- File → Settings → Build, Execution, Deployment → Build Tools → Gradle
- Gradle Projects → Click + → Select
algorithms-javadirectory - Or refresh with correct path:
cd algorithms-java ./gradlew --refresh-dependencies clean build
- Go to File → Project Structure
- Check Modules → algorithms-java
- Ensure Test Sources Root points to
src/test/java - Apply and restart IntelliJ
- File → Settings → Editor → File Types
- Add patterns to Ignored Files and Folders:
*.class*Test.html*.java.html
- File → Project Structure → Modules
- Click + → Import Module
- Select
algorithms-java/build.gradle - Import as Gradle project
- Use
devtask for regular development (faster thanbuild) - Use
quicktask for compile-only checks - Keep build artifacts excluded from version control and search
- Use IntelliJ's built-in test runner instead of Gradle for individual tests
- Console: Coverage percentage printed after every test run
- Local HTML: Available in
build/reports/jacoco/test/html/index.html - CI/CD: Automatically pushed to Coveralls on GitHub Actions