Conversation
sarahxsanders
added a commit
that referenced
this pull request
Jul 22, 2026
Adds Java (server) as a supported framework, stacked on the Rust framework PR: - Integration.java enum entry ordered after kmp/swift/android — those claim gradle projects first — and before the language fallbacks - JAVA_AGENT_CONFIG in src/frameworks/java/ — claims pom.xml unconditionally (Maven is unambiguously JVM backend) and root gradle files only when they carry no Android/KMP plugin markers and no AndroidManifest.xml subtree exists; gathers buildTool (maven | gradle) as agent context; installs by editing the build file with com.posthog:posthog-server then resolving with mvn install / gradle build - detectJavaPackageManagers detector (Maven via pom.xml, Gradle fallback reusing gradlePackageManager) + FRAMEWORK_REGISTRY entry - No bash-fence changes needed: mvn/mvnw and gradle/gradlew grammars already exist from Android/KMP - Pins framework: java on a new integration-java entry in the variant-resolution contract test, matching context-mill PR #270 which must release before this merges - Marks pom.xml as a real framework target in the agentic manifest comment, leaving .NET as the only manifest without a target Generated-By: PostHog Code Task-Id: 9c949855-7611-48f2-b8b5-7aa4112543e5
sarahxsanders
added a commit
that referenced
this pull request
Jul 22, 2026
Adds Java (server) as a supported framework, stacked on the Rust framework PR: - Integration.java enum entry ordered after kmp/swift/android — those claim gradle projects first — and before the language fallbacks - JAVA_AGENT_CONFIG in src/frameworks/java/ — claims pom.xml unconditionally (Maven is unambiguously JVM backend) and root gradle files only when they carry no Android/KMP plugin markers and no AndroidManifest.xml subtree exists; gathers buildTool (maven | gradle) as agent context; installs by editing the build file with com.posthog:posthog-server then resolving with mvn install / gradle build - detectJavaPackageManagers detector (Maven via pom.xml, Gradle fallback reusing gradlePackageManager) + FRAMEWORK_REGISTRY entry - No bash-fence changes needed: mvn/mvnw and gradle/gradlew grammars already exist from Android/KMP - Pins framework: java on a new integration-java entry in the variant-resolution contract test, matching context-mill PR #270 which must release before this merges - Marks pom.xml as a real framework target in the agentic manifest comment, leaving .NET as the only manifest without a target Generated-By: PostHog Code Task-Id: 9c949855-7611-48f2-b8b5-7aa4112543e5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Created a tracker that is called through:
and runs parallel to the agent to benchmark things like:
llm-promptsWhat's cool is that we can use a similar pattern to build all kinds of plugins and instrumentation, so I might generalize this in the future to an interface...