Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Profile activation for WF app server doesn't properly work for Windows #21284

@mabartos

Description

@mabartos

Before reporting an issue

  • I have searched existing issues
  • I have reproduced the issue with the latest release

Area

testsuite

Describe the bug

As the documentation for the activeByDefault activation element states:
'This profile will automatically be active for all builds unless another profile in the same POM is activated using one of the previously described methods. All profiles that are active by default are automatically deactivated when a profile in the POM is activated on the command line or through its activation config.'

In the testsuite/integration-arquillian/servers/app-server/jboss/pom.xml, profile windows-properties-cli is implicitly enabled and the activeByDefault for WF app server is ignored same as the whole module.

You can see the WildFly app server module will not be built:

image

Version

999

Expected behavior

The module is built on Windows

Actual behavior

The module is not built on Windows

How to Reproduce?

mvn clean install -Dtest=UserTest -f testsuite/integration-arquillian/pom.xml

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions