8000 Some downstream native configs initialize JUnit classes at build time in production · Issue #3707 · googleapis/sdk-platform-java · GitHub
[go: up one dir, main page]
Skip to content
Some downstream native configs initialize JUnit classes at build time in production #3707
New issue
New issue
Open
Open
Some downstream native configs initialize JUnit classes at build time in production#3707
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
@diegomarquezp

Description

@diegomarquezp
diegomarquezp
opened on Mar 17, 2025

From #3674

Some libraries mark JUnit classes for initialization at build time in its production native properties file.

For example: https://github.com/googleapis/java-spanner-jdbc/blob/fa65ead20018c083749bb1bd1cc1993f48745ef9/src/main/resources/META-INF/native-image/com.google.cloud/google-cloud-spanner-jdbc/native-image.properties#L15

I tried moving it to a test-only config file (src/test/resources...) but the image creation would fail asking to specify the JUnit classes to be initialized at runtime.

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0