1. IDE Project Generation Commands (IntelliJ & Eclipse)

Maven CommandDescription
mvn eclipse:eclipsegenerates Eclipse project files (alternatively, you could use m2e)
mvn idea:ideagenerates IDEA IntelliJ project files

2. Maven Build, Unit Test, and Integration Test Workflows

Maven Command (1)Description
mvnruns the root pom's default goal, verify apache-rat:check. RAT is informational and currently reports violations, so a bare mvn ends red; run an explicit goal instead
mvn clean installperforms a full build including the unit tests (about 4 minutes with the forked, partitioned surefire run)
mvn clean install -DskipTestsperforms a build, compiling the tests and building the test-jars but not running them. Faster; not for final checks
mvn clean install -Dmaven.test.skipdo not use: it also skips building wikantik-main's test-jar, which wikantik-admin-mcp, wikantik-tools, wikantik-knowledge and the IT modules depend on, so a full-reactor build fails
mvn clean install -T 1C -DskipITsparallel unit-test build (what phase 1 of bin/run-tests.sh runs)
mvn clean testcompiles the source and executes the tests
mvn test -Dtest=MarkdownRendererTestrun just a single test class
mvn test -Dtest=MarkdownRendererTest#testMarkupSimpleMarkdownrun just a single test within a test class
mvn test -pl wikantik-main -Dtest=JDBCUserDatabaseTestrun one test class in one module (tests that touch a database start a pgvector container through Docker)
mvn test -Dtest=TestClassName#methodName -Dmaven.surefire.debugdebug a test in Eclipse or IDEA to see why it's failing (see http://www.jroller.com/gmazza/entry/jpa_and_junit#debugging)
mvn compile -pl wikantik-main -qcompile-check one module; after a signature change use test-compile instead, because compile skips the test sources
bin/agent-build.sh start unit -- mvn clean install -DskipITsrun a build that may exceed ~5 minutes detached from the shell; poll with bin/agent-build.sh status unit / wait unit 540
bin/deploy-local.sh, bin/redeploy.shrun Wikantik on a local Tomcat 11 as the ROOT context at http://localhost:8080/ (first time / after config changes, and the fast routine redeploy). The Cargo run goal is not wired into the war module; Cargo only launches Tomcat for the IT modules
bin/run-tests.sh --parallel 4the canonical pre-commit gate: all unit tests, then the five IT modules in one 4-wide reactor (needs Docker)
mvn clean install -Pintegration-testsperforms a build, enabling the integration tests under wikantik-it-tests. Do not add -T to a raw invocation; parallel ITs are supported only through bin/run-tests.sh --parallel N
mvn test -Dtest=MemoryProfiling(from wikantik-main module) runs a memory profiling test

(1) -T 1C can be added to the unit-test builds above in order to run a parallel build, thus decreasing build time, i.e., mvn clean install -T 1C -DskipITs.

3. Code Coverage (JaCoCo), PMD Complexity Gate, and Site Reports

Maven CommandDescription
mvn apache-rat:checkcreates an Apache RAT report. Informational only: it is not bound to any lifecycle phase and currently reports violations (docs, scripts and the frontend carry no license headers). See: http://creadur.apache.org/rat/apache-rat-plugin/plugin-info.html
mvn clean install -DskipITs -Pcoveragegenerates the JaCoCo coverage report (aggregated in wikantik-coverage-report) and enforces each module's line-coverage floor
mvn pmd:check -Pcomplexity-gatethe CI complexity ratchet: fails on any new PMD design-rule violation not in build-support/pmd-complexity-baseline.properties (CI runs it with -fn and requires BUILD SUCCESS)
bin/site.shbuilds the full code-health site (coverage, coupling, PMD, CPD, SpotBugs, tests, dependencies) into target/staging/index.html
mvn javadoc:javadoccreates javadocs adding some UML class/package level diagrams
mvn sonar:sonargenerates a Sonar report. Expects a Sonar server running at http://localhost:9000/

Cluster Hub: Wikantik Platform Development Hub: Architecture, MCP Protocols, and Agent Briefings (wikantik-development)