activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: [DISCUSS] Create an ActiveMQ Web Console sub-project
Date Mon, 27 Jan 2014 11:09:49 GMT
This is one of the big technical issues with the existing web console

https://issues.apache.org/jira/browse/AMQ-4994

If you guys want to do some work for the console and the community you care
so much about, this one is the first to be fixed before we can move on with
any release.

Regards
--
Dejan Bosanac
----------------------
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosanac@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/


On Sat, Jan 25, 2014 at 9:49 PM, Hadrian Zbarcea <hzbarcea@gmail.com> wrote:

> +1. Agree. Simple and clear.
> Hadrian
>
>
> On 01/25/2014 03:36 PM, James Carman wrote:
>
>> I think the console should be part of the main distribution.  They should
>> be released together.  Release early, release often.
>>
>> On Saturday, January 25, 2014, Robert Davies <rajdavies@gmail.com> wrote:
>>
>>  The recent poll [1] and discussions [2] around what to do with the
>>> current
>>> ActiveMQ web console demonstrated there’s a mix bag of views. There are
>>> developers who passionately believe that the current Web Console is a
>>> large
>>> technical debt on the project, hasn’t been actively developed for years
>>> and
>>> is a security risk - whilst others believe it benefits users immensely to
>>> have such a web console available.
>>>
>>> What I would like to propose is that the Web Console is moved to a sub
>>> project of ActiveMQ - where those interested in maintaining and
>>> developing
>>> it can work independently of the ActiveMQ broker release. Ideally there
>>> would be collaboration - so that the Web console could be released in the
>>> same time frame as every new minor and major release of the broker.
>>> However, having it as a sub project will also allow for it to be released
>>> independently - so that if folks want to iterate releases of the web
>>> console whilst they improve it or to fix issues as they arise they can.
>>> It
>>> also has the benefit of freeing up ActiveMQ developers who want to
>>> concentrate on the core broker functionality.
>>>
>>> This is a compromise, but I believe its the best way forward. What do you
>>> guys think ?
>>>
>>> thanks,
>>>
>>> Rob
>>>
>>> [1] https://www.mail-archive.com/dev@activemq.apache.org/msg37711.html
>>> [2]
>>> http://activemq.2283324.n4.nabble.com/DISCUSS-Remove-the-
>>> old-ActiveMQ-Console-td4675925.html
>>>
>>> Rob Davies
>>> ————————
>>> Red Hat, Inc
>>> http://hawt.io - #dontcha
>>> Twitter: rajdavies
>>> Blog: http://rajdavies.blogspot.com
>>> ActiveMQ in Action: http://www.manning.com/snyder/
>>>
>>>
>>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message