I agree, this seems like the best approach so far.
On 7 Jan 2014, at 23:27, Christian Posta wrote:
> +1 @ Claus, Jim, and Tim's thread of the discussion.
>
> Moving the console to a subproject separates the code out enough and
> makes it "less intimidating" to those in the community that would
1. git clone https://git-wip-us.apache.org/repos/asf/activemq.git
2. mvn install
FAILURE!
Running org.apache.activemq.transport.mqtt.MQTTTest
Tests run: 19, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 43.765 sec <<<
FAILURE!
Running org.apache.activemq.transport.mqtt.PahoMQTNioTTest
Tests ru
+1 @ Claus, Jim, and Tim's thread of the discussion.
Moving the console to a subproject separates the code out enough and
makes it "less intimidating" to those in the community that would like
to approach it and contribute. Then have one distro that's "headless"
with the option of using whatever c
[
https://issues.apache.org/jira/browse/AMQ-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864819#comment-13864819
]
Ulrich Romahn commented on AMQ-4961:
Unfortunately, the leveldbjni-all does not contain
[
https://issues.apache.org/jira/browse/AMQ-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Romahn resolved AMQ-4961.
Resolution: Won't Fix
Please see my last comment for the reason to actually resolve this issue as
"w
On 01/06/2014 03:06 AM, Claus Ibsen wrote:
Hi
I think the old web console should be moved into a sub-project of ActiveMQ.
Other ASF projects like Felix [1], Karaf [2], etc does this with their
web-consoles.
That may also make it easier for people to contribute to the
web-console as a sub-projec
On Jan 5, 2014, at 8:54 AM, Robert Davies wrote:
> Hi Jeff,
>
> Perhaps the best way forward would be to have 2 distros of ActiveMQ - one
> without the console, and one with the old console - with clear warnings that
> it is not maintained etc.
Personally, I really like this option.A “m
Of course, by shipping with no console, stopping development of the
current one, and with hawt.io already having a working console, I
wonder where we are going to be pointing folks?
On Tue, Jan 7, 2014 at 2:48 PM, Jim Gomes wrote:
> +1 the ideas that Claus presented below. I like the idea of a s
[
https://issues.apache.org/jira/browse/AMQ-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864648#comment-13864648
]
Timothy Bish commented on AMQ-4953:
---
I'm not sure this is a bug as I don't see anywhere in
+1 the ideas that Claus presented below. I like the idea of a simple
drop-in install and a level playing field for replacement consoles. By
having a default "headless" install, the security of a production
deployment goes way up.
On Mon, Jan 6, 2014 at 12:06 AM, Claus Ibsen wrote:
> Hi
>
> I
Gary Tully created AMQ-4964:
---
Summary: org.apache.activemq.bugs.ConnectionPerMessageTest is very
slow - seems to point to lock contention on close
Key: AMQ-4964
URL: https://issues.apache.org/jira/browse/AMQ-4964
[
https://issues.apache.org/jira/browse/AMQ-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lionel Cons updated AMQ-4963:
-
Description:
There seems to be a typo in
activemq-kahadb-store/src/main/proto/journal-data.proto. This fil
Lionel Cons created AMQ-4963:
Summary: Typo in journal-data.proto
Key: AMQ-4963
URL: https://issues.apache.org/jira/browse/AMQ-4963
Project: ActiveMQ
Issue Type: Bug
Reporter: Lionel
13 matches
Mail list logo
