Skip to content

Multi-language generation is blocked on the system under test #12

Description

@FelixTJDietrich

The dataset is Java-only and the adapter now carries language through typed target parameters with per-case overrides, so the harness side is ready. Artemis is not.

On the current Artemis branch, LanguageGenerationProfile admits JAVA only, restricted to MAVEN_MAVEN and PLAIN_MAVEN. Beyond adding the language there, a second language needs: per-language layout, test-framework and annotation guidance in the generation prompt; the draft-creation precondition check to consult the profile rather than a literal Java check; per-language source-path sets for the scaffold strip (a named-file strip, not an extension sweep, which would delete __init__.py and break Python package discovery); a worked reference sample and build-readiness fixture, which currently return empty for anything non-Java; and a decision about staged generation, which is gated to Java and would otherwise silently run a different treatment under the same arm identity.

Until then a multi-language dataset cannot be run, and docs/SUT-REQUIREMENTS.md records this as part of the Artemis conformance gap.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions