You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2021/08/24 16:33:00 UTC

[jira] [Resolved] (ARTEMIS-3440) separate effect of -Pdev from -Ptests

     [ https://issues.apache.org/jira/browse/ARTEMIS-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell resolved ARTEMIS-3440.
-------------------------------------
    Resolution: Fixed

> separate effect of -Pdev from -Ptests
> -------------------------------------
>
>                 Key: ARTEMIS-3440
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3440
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Major
>             Fix For: 2.19.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently the build has RAT and checkstyle executions always configured, but uses some artemis specific properties to skip them by default. These properties are then used in the 'tests', fast-tests', and 'dev' profiles to enable the checks when the profile is activated.
> This approach means that:
>  - If you use the test profiles (needed to run tests), you get the dev checks even if you dont want.
>  - You cant skip or not-skip the checks even with their own well known skip properties.
>  - You cant run the check directly with its own mojo, without first hunting down an artemis specific property to also not-skip them so they actually run.
> The former in particular can be annoying when developing and running specific tests repeatedly, as it adds >10sec before the execution of a specified integration test for example.
> It also prevents an improvement I was looking to do for the GHA CI jobs where the checks are run in isolation from the tests (ensures the tests start and complete as fast as possible, speeding things up overall, makes the checks not prevent the tests running if they fail, and vice versa ensures the checks occur regardless of the tests failing which happens somewhat often at times).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)