[
https://issues.apache.org/jira/browse/ARTEMIS-3650?focusedWorklogId=710067&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-710067
]
ASF GitHub Bot logged work on ARTEMIS-3650:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 17/Jan/22 17:29
Start Date: 17/Jan/22 17:29
Worklog Time Spent: 10m
Work Description: gemmellr commented on pull request #3919:
URL:
https://github.com/apache/activemq-artemis/pull/3919#issuecomment-1014761103
There are further changes that it could be made later, e.g. the change notes
the use of jetty-all needed a slight workaround rather than being treated as
any regular transitive dep (it brings in the duplicate individual dependencies
for everything it contains, or possibly even more), and was actually described
as not being for end use by the jetty folks. I think shifting to the needed
individual jetty bits should be a separate change though so didnt look to
include that. There are possibly also some deps the assembly module is still
handling that should be covered in related modules themselves instead.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 710067)
Time Spent: 20m (was: 10m)
> rework assembly creation to simplify and ease maintenance
> ---------------------------------------------------------
>
> Key: ARTEMIS-3650
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3650
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.20.0
> Reporter: Robbie Gemmell
> Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The current assembly creation process is rather verbose, and can also be
> somewhat problematic as result of effectively specifying every jar to
> include, often meaning it can both fail to pick up certain changes that occur
> in dependencies of the maven modules that then breaks things (e.g
> ARTEMIS-3616), or in turn also masking issues in the modules that could
> otherwise be visible and noticed in the assembly otherwise (e.g some of the
> scope et changes made in the coming diff).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
