[jira] [Work logged] (ARTEMIS-3783) rationalise config for alternate jakarta spec versions

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-3783?focusedWorklogId=759130&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-759130 ]

ASF GitHub Bot logged work on ARTEMIS-3783:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Apr/22 11:28
            Start Date: 20/Apr/22 11:28
    Worklog Time Spent: 10m 
      Work Description: gemmellr opened a new pull request, #4033:
URL: https://github.com/apache/activemq-artemis/pull/4033

   Group the alternative versions into a related property, easily found at the root near the base version property, and perform the overrides using that. Remove superfluous version entrys from dependency uses, its already covered by the version properties and dependencyManagement.




Issue Time Tracking
-------------------

            Worklog Id:     (was: 759130)
    Remaining Estimate: 0h
            Time Spent: 10m

> rationalise config for alternate jakarta spec versions
> ------------------------------------------------------
>
>                 Key: ARTEMIS-3783
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3783
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>    Affects Versions: 2.21.0
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Major
>             Fix For: 2.22.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are specific modules in the build using Jakarta EE 9 based artifacts, whereas the rest use the Jakarta EE8 artifacts. As such, these various modules are overriding the version of the spec jars accordinglyto ensure the appropriate one is used/depended on.
> They currently all do this by hard coding the different override version in each module, whereas the base version config is nicely dependency managed from a single property at the root. More instances of this are being added as time goes, making the situation worse. We should rationalise the config for the alternate jakarta spec versions to their own single properties to simplify things, aligning their uses in the codebase and make things easier to maintain later.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)