Skip to content

Make Surefire/Failsafe configuration for Java 25 more robust #51811

@Sanne

Description

@Sanne

Description

A follow up to #50915 : that approach worked well in projects that don't have a Surefire/Failsafe configuration, but:

  • I wasn't very careful in separating configuration of Surefire vs Failsafe
  • Maven was completely ignoring it if an argLine was already defined in the project

Implementation ideas

As discussed on #dev > Maven Surefire auto-config : we introduce an explicitly separated property quarkusSurefireArgLine as suggested by @aloubyansky ( and quarkusFailsafeArgLine for failsafe).
In addition, if there is no configuration at all then we write into the default properties.

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions