* Align README MCP section with MCP.md - Fix tool discovery model: tools/list returns one tool (java_call with embedded catalog), not per-method named tools - Fix tools/call example to use java_call + callContent, not tool name - Rename "Fallback Tool" section — java_call is the only MCP tool - Add ibs_diagnostics, IBS.MCP.PRECHAIN, IBS.MCP.REQUIRE_JAVADOC - Fix dependency version 2.11.18 → 2.11.19 to match MCP.md - Update TOC Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Update docs to version 3.11.0 Add 3.11.0 release notes entry covering MCP doc corrections, new env vars, dependency bumps, and CI GPG fix. Update version references in README and MCP.md from 2.11.19 to 3.11.0. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Simplify 3.11.0 release notes to high-level summary Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Add issue #12 reference to 3.11.0 MCP release note Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Bump GitHub Actions to v5 to fix Node.js 20 deprecation warning actions/checkout, actions/setup-java, and actions/cache all moved from v4 (Node.js 20) to v5 (Node.js 24). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Bump actions/upload-artifact to v5 to fix Node.js 20 deprecation warning Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * [maven-release-plugin] prepare release parent-3.11.0 * [maven-release-plugin] prepare for next development iteration * Add missing Javadoc @param and @return to MCPRequestHandler#handle Fixes Javadoc warnings raised during the release build. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Update version to 3.11.1 in docs and add Central promotion step - Bump all doc version references from 3.11.0 to 3.11.1 - Add POST /manual/upload step to release workflow to trigger Central Publisher Portal promotion after staging deploy Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Add Central promotion step to deploy workflow Mirrors the same POST /manual/upload step added to the release workflow. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Remove Central promotion step from deploy workflow Snapshot deploys go directly to the snapshot repository — no staging repository is created, so the promotion POST returns 400. The promotion step belongs only in the release workflow. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * [maven-release-plugin] prepare release parent-3.11.1 * [maven-release-plugin] prepare for next development iteration * Fix CI badge staleness for SonarCloud quality gate and codecov (#22) Trigger SonarCloud analysis on push to main (not just PRs) so the quality gate badge stays current after merges. Remove dead jacoco log step that referenced a non-existent step output. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> * Update dependency org.testng:testng to v7.12.0 (#21) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * Update dependency org.mockito:mockito-core to v5.23.0 (#20) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * Update log4j2 monorepo to v2.25.4 (#23) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * Update actions/checkout action to v6 (#24) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * Expose auto-discovered methods as individual MCP tools (hybrid approach) (#35) * Expose auto-discovered methods as individual MCP tools (hybrid approach) Previously all auto-discovered methods were embedded as plain text in java_call's description. With 2000+ methods this exceeded LLM context windows and got truncated, making method discovery impossible without trial-and-error 404 guessing. Each public static method is now exposed as its own tool in tools/list (name: ClassName_methodName, inputSchema with arg0/arg1/... params). Individual tool calls are routed through handleIndividualToolCall() which builds a synthetic single-step callContent and delegates to handleJavaCall() so PRECHAIN is applied automatically. java_call is retained for multi-step chains, overloaded/instance methods, and any case where step B needs the live Java object returned by step A. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Add architecture diagram to MCP method discovery section Mermaid flowchart showing the startup package scan that populates tools/list, and the two per-call paths (individual tool and java_call) converging on handleJavaCall() through the isolated classloader. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Fix coverage gap: replace JSON schema parsing with programmatic map builders The constructor's try-catch for JsonProcessingException was dead code — the schemas are hardcoded constants that never fail to parse. handleIndividualToolCall's catch was also dead code since handleJavaCall catches its own exceptions internally. Replaced both with no-exception-possible patterns to eliminate the uncovered lines. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> * Prepare release 3.11.2 - Add 3.11.2 release notes entry (hybrid MCP tool discovery, dependency bumps, CI) - Update version references in README and docs/MCP.md from 3.11.1 to 3.11.2 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Document release process in CLAUDE.md Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Update README MCP section for hybrid tool discovery (3.11.2) The Discovering Tools and Calling a Discovered Tool sections still described the old single-java_call approach. Updated to reflect that tools/list now returns one named tool per auto-discovered method plus java_call and ibs_diagnostics, and that individual tools can be called directly for stateless single-method invocations. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Fix stale version in /test endpoint response example (3.11.2) The health check response example still showed 2.11.16 instead of 3.11.2. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * [maven-release-plugin] prepare release parent-3.11.2 * [maven-release-plugin] prepare for next development iteration * Migrate HTTP layer from Spark Java to Javalin 6 (issue #38) (#43) * Add Java version migration research document for issue #25 Captures compatibility analysis across four scenarios (host on Java 17+, host on Java 8, IBS upgraded to Java 17, why not Java 21) and a recommended two-step migration path: Java 17 classifier JAR first, Spring Boot 3.x replacement second. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Expand Java migration research with compatibility matrix, LTS analysis, and revised two-priority plan Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Update files-to-change section to reflect Javalin migration scope Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Migrate HTTP layer from Spark Java to Javalin 6 (issue #38) - Replace spark-core 2.9.4 + javax.servlet-api with javalin 6.3.0 + ssl-plugin 6.3.0 - Rewrite IntegroAPI: Spark static DSL → Javalin instance API; multipart via jakarta.servlet Part; SSL via SslPlugin; startServices() now returns Javalin instance - Update MCPRequestHandler: handle(Request, Response) → handle(Context) - Add setAccessible(true) in CallContent for Java 17+ strong encapsulation - Update 4 test files: replace Spark.awaitInitialization/stop with Javalin app.stop() All 279 tests pass. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Add tests to improve patch coverage for Javalin migration - MCPRequestHandler: cover parse error (malformed JSON), missing method field, missing tool name, and .well-known/oauth-authorization-server endpoint - IntegroAPI: cover IBSRunTimeException handler via invalid DURATION assertion key 284 tests pass. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Update docs for Javalin 6 migration (issue #38) - README.md: replace Spark/javax.servlet conflict note with Javalin 6 / jakarta.servlet guidance - docs/Technical.md: add HTTP Framework section documenting Javalin 6, Jetty 11, and migration differences from Spark - docs/JavaMigration.md: mark Priority 1 as DONE, update compatibility matrix to show Javalin 6 as current Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Add Java version compatibility matrix to README Placed directly after the integration model descriptions so users can immediately see which IBS release works with their Java version. Links to docs/JavaMigration.md for the full analysis and Priority 2 roadmap. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> * Clarify release trigger in CLAUDE.md Release is kicked off via GitHub Actions (Release-BridgeService workflow, workflow_dispatch), not by running Maven commands locally. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Prepare release 3.11.3 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * [maven-release-plugin] prepare release parent-3.11.3 * [maven-release-plugin] prepare for next development iteration * Add demo usage examples to Running a DEMO section (issue #50) (#51) * Add demo usage examples to Running a DEMO section (issue #50) Single startup command enables both REST and MCP. Three use-case tables show REST payload + AI prompt side-by-side: string argument call, list return, and call chaining. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Restructure demo tables: Call + Response rows, REST vs MCP columns Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Move JSON payloads to code blocks above tables for readability Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Replace tables with linear REST/MCP/Response format per use case Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> * Add three-level Javadoc quality gate for MCP tool discovery (issue #40) (#52) * Add three-level Javadoc quality gate for MCP tool discovery (issue #40) Extends IBS.MCP.REQUIRE_JAVADOC from a boolean to a three-value setting: - false: expose all public static methods - true: requires non-empty Javadoc comment (previous default) - strict (new default): requires comment + @param for every parameter Methods missing @param tags previously exposed "description":"String" as the parameter description, giving AI agents no useful guidance. The strict default prevents such tools from appearing in tools/list. Startup log now reports the active gate level and its effect. Diagnostics field renamed from javadocRequired (boolean) to javadocQualityGate (string) to accurately reflect the three-way setting. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Report skipped method count in MCP tool discovery log The discovery log now shows how many methods were filtered out by the active quality gate, e.g. "21 registered, 5 skipped by quality gate (strict)". Added skippedCount field to DiscoveryResult for use by callers. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Improve coverage for Javadoc quality gate and document coverage rules Add tests for the 'true' mode path of shouldSkipForJavadoc (previously unreachable since the default changed to 'strict') and for skippedCount reporting. Update CLAUDE.md with explicit 80% patch coverage rule so future contributors understand what codecov/patch enforces. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Fix codecov/patch coverage gaps in Javadoc quality gate Three gaps addressed: - Lines 119-124: overloaded-method path with unique param counts was never exercised; added overLoadedMethodDifferentArity(String) and (String,String) to SimpleStaticMethods to trigger this path - Lines 143-144: MCPRequestHandler startup log 'false'/'true' ternary branches were only reached under strict mode; added handler construction tests for both modes - Lines 202-203: hasAdequateJavadoc exception catch now covered via Mockito MockedStatic with thenAnswer/thenThrow chaining Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Fix codecov/patch: inline hasAdequateJavadoc to cover exception path hasAdequateJavadoc previously called hasJavadoc() first then called RuntimeJavadoc.getJavadoc() a second time inside its own try block. The Mockito thenAnswer(callRealMethod).thenThrow() pattern failed to delegate the first call correctly in static mock mode, so hasJavadoc() returned false and the catch block was never reached. Inline the comment check into a single try/catch so a simple thenThrow mock hits the catch block directly, covering lines 202-203. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> * Prepare release 3.11.4 * Update release process: add PR step and conflict resolution guidance * [maven-release-plugin] prepare release parent-3.11.4 * [maven-release-plugin] prepare for next development iteration --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: adobe-bot <Grp-opensourceoffice@adobe.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Add examples of usage in Running a Demo in the README #50

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions