[
https://issues.apache.org/jira/browse/ARTEMIS-4680?focusedWorklogId=915295&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-915295
]
ASF GitHub Bot logged work on ARTEMIS-4680:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Apr/24 12:12
Start Date: 18/Apr/24 12:12
Worklog Time Spent: 10m
Work Description: gemmellr commented on code in PR #3:
URL:
https://github.com/apache/activemq-artemis-console-plugin/pull/3#discussion_r1570604745
##########
artemis-console-distribution/pom.xml:
##########
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="UTF-8"?>
Review Comment:
As before, we should probably avoid `artemis-console`, because it does
clash, and though its only a pom it is still going to be published.
We cant 'go backwards' for versions as it creates a significant reporting
problem for bugs and CVEs around what is/isnt affected...there are also many
newer broker-versioned released of an '`artemis-console`' that already exist
with a higher version, so we would never be able to use those versions and
would have a right mess when that time came. The only way we can use
`artemis-console` as a module would be to start this repo's releases at a
version above the range that will ever be occupied by those still-ongoing
releases of the existing `artemis-console` module.
https://repo1.maven.org/maven2/org/apache/activemq/artemis-console/
Since it is really a different artifact entirely, that is not actually
having any jar etc deployed for it (unlike previously), and is being released
independently of the broker going forward and so wont use matching
broker-versions...just avoiding the already-used `artemis-console` name seems
to make more sense than version foolery. Someone today might reference
`artemis-console` as a module...it doesnt seem like anyone should want to in
future., however they might be confused into by reuse of the module name for
something different than before.
My comment was that it doesnt really matter what we call it, as its just a
pom for doing some local build, and not a module users will refer to...what
about `artemis-console-build`? `artemis-console-extension`?
Issue Time Tracking
-------------------
Worklog Id: (was: 915295)
Time Spent: 5h 20m (was: 5h 10m)
> Upgrade the console to use HawtIO 4
> -----------------------------------
>
> Key: ARTEMIS-4680
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4680
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Web Console
> Reporter: Andy Taylor
> Assignee: Andy Taylor
> Priority: Major
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> The current console is based upon HawtIO 1 which in turn is built on
> Bootstrap. Bootstrap is old and no longer actively being maintained.
>
> This improvement is to migrate the current console to use HawtIO 4 which i
> based on Typescript, react and Patternfly.
>
> A WIP can be found
> [here|https://github.com/andytaylor/activemq-artemis/tree/artemis-console-ng]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
