[
https://issues.apache.org/jira/browse/AMQ-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299885#comment-14299885
]
Tamas Cserveny commented on AMQ-2798:
-
I just met this problem in our environment.
My
+1
On Fri, Jan 30, 2015, 10:34 PM Claus Ibsen claus.ib...@gmail.com wrote:
Hi
+1
Tested against Camel in Action source code also.
On Fri, Jan 30, 2015 at 3:00 PM, Gary Tully gary.tu...@gmail.com wrote:
Hi folks,
I've just cut a third release candidate for the long-awaited 5.11.0
+1 (non-binding)
Regards
Krzysztof
On 30.01.2015 15:00, Gary Tully wrote:
Hi folks,
I've just cut a third release candidate for the long-awaited 5.11.0 release.
This release has more than 120 bug fixes and improvements.
-note-
this candidate includes the fix for the 'reliably' broken
[
https://issues.apache.org/jira/browse/AMQ-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299963#comment-14299963
]
Tamas Cserveny commented on AMQ-2798:
-
Actially there is a general problem behind the
+1
On 01/30/2015 09:00 AM, Gary Tully wrote:
Hi folks,
I've just cut a third release candidate for the long-awaited 5.11.0 release.
This release has more than 120 bug fixes and improvements.
-note-
this candidate includes the fix for the 'reliably' broken test case from rc2
however there can
[
https://issues.apache.org/jira/browse/AMQ-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14300031#comment-14300031
]
Arthur Naseef commented on AMQ-5552:
There is good and bad here. I like the idea of a
+1, this seems like a great idea Art.
I'll be glad to help with this.
On Jan 31, 2015, at 5:25 PM, artnaseef a...@artnaseef.com wrote:
*Background*
As we all know, ActiveMQ tests take a very long time to execute, and a
number of the tests have been unreliable. Personally, it was ActiveMQ
*Overview*
Defining a consistent approach to tests for releases will help us both
near-term and long-term come to agreement on (a) how to maintain quality
releases, and (b) how to improve the tests in a way that serves the needs of
releases.
As a general practice, tests that are unreliable raise
We have been through that exercise already on activemq-6. Perhaps it
would be a better use of resources if we worked towards activemq-6?
With hornetq (now activemq-6) we differentiated unit-tests,
integration tests, soak tests and performance tests.
When you do a build you won't do the entire
*Background*
As we all know, ActiveMQ tests take a very long time to execute, and a
number of the tests have been unreliable. Personally, it was ActiveMQ that
lead me to learn maven's skip test features early on because I would not
wait hours to get a small change into a build during development,
10 matches
Mail list logo
