[GitHub] activemq-artemis pull request: Ensure tests use proper directory
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/268 Ensure tests use proper directory You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/268.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #268 commit c348cd2ad4729c87fa2d984df78fc8b96a6772d1 Author: jbertram jbert...@apache.org Date: 2015-05-19T16:11:47Z Ensure tests use proper directory --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: Changing host to 0.0.0.0
Github user jbertram commented on the pull request: https://github.com/apache/activemq-artemis/pull/261#issuecomment-103563394 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: ACTIVEMQ6-110 getDeliveringMessages...
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/265 ACTIVEMQ6-110 getDeliveringMessages() broken You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis deliveringIssue Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/265.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #265 commit 8561d60f54dfec1ea9efc34e90c175dfdaa08184 Author: jbertram jbert...@apache.org Date: 2015-05-18T18:57:05Z ACTIVEMQ6-110 getDeliveringMessages() broken --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: Initial commit of the hacking guide
Github user jbertram closed the pull request at: https://github.com/apache/activemq-artemis/pull/263 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: Initial commit of the hacking guide
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/263 Initial commit of the hacking guide You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis hacking_guide Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/263.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #263 commit 6083aa98a2bc8bf4fe9087185d8fb4141613a47d Author: jbertram jbert...@apache.org Date: 2015-05-13T17:49:42Z Initial commit of the hacking guide --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: Make CLI print data more friendly
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/257 Make CLI print data more friendly You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/257.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #257 commit 271c2d1ccffe6fd6606dcedfa0649ba8e6f50fe7 Author: jbertram jbert...@apache.org Date: 2015-05-13T15:02:54Z Make CLI print data more friendly --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: Make CLI print data more friendly
Github user jbertram closed the pull request at: https://github.com/apache/activemq-artemis/pull/257 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: Change default profile from 'dev' t...
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/241 Change default profile from 'dev' to 'distro' You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/241.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #241 commit 90d90b5e1869a6ad13d5a896dc58c434401b6b11 Author: jbertram jbert...@apache.org Date: 2015-05-11T14:27:29Z Change default profile from 'dev' to 'distro' --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: Fix ref to old version in doc
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/242 Fix ref to old version in doc You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/242.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #242 commit f26d99cb585e22a62b006333dcaabd43e3269a96 Author: jbertram jbert...@apache.org Date: 2015-05-11T14:33:56Z Fix ref to old version in doc --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: Fix ref to old distribution
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/243 Fix ref to old distribution You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/243.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #243 commit 7d393c25696a1445c1adee9e8c5881eb872e5f74 Author: jbertram jbert...@apache.org Date: 2015-05-11T15:48:19Z Fix ref to old distribution --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: Clean up 'ActiveMQ' refs in literal...
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/246 Clean up 'ActiveMQ' refs in literals You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/246.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #246 commit 2cbeedab895d94c83f16eda6694b2709514ca7da Author: jbertram jbert...@apache.org Date: 2015-05-11T16:23:10Z Clean up 'ActiveMQ' refs in literals --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: HornetQ Protocol Support
Github user jbertram commented on the pull request: https://github.com/apache/activemq-artemis/pull/227#issuecomment-99900168 Martyn, can you rebase your PR? There are some fixes merged recently that you need for the PR build to finish successfully. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: Exclude keystore types from RAT che...
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/230 Exclude keystore types from RAT check You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/230.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #230 commit 330372542bdc9d06efc4f508bee223632a7bb34d Author: jbertram jbert...@apache.org Date: 2015-05-06T13:38:05Z Exclude keystore types from RAT check --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: A bunch of commits to fix Maven/bui...
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/231 A bunch of commits to fix Maven/build stuff You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/231.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #231 commit 4735d38d7bfdbbed6d5b2f0fae6c6c6629a5dc12 Author: jbertram jbert...@apache.org Date: 2015-05-06T16:15:33Z Update surefire plugin versions commit e42d742af0cde66d54a6651488a6080a144a2180 Author: jbertram jbert...@apache.org Date: 2015-05-06T16:38:04Z Disable license and checkstyle checks by default; add a new 'dev' profile with license and checkstyle checks enabled commit ad28e59e9ca51e2f128452db47e21db160631f52 Author: jbertram jbert...@apache.org Date: 2015-05-06T19:18:41Z Enable extra tests in 'extra-tests' profile commit 7eabe3a171a96a6f869cda44f7ef1913f64b1a33 Author: jbertram jbert...@apache.org Date: 2015-05-06T19:19:57Z Drastically simplify git ignores commit 8d3d8eda73a373238f873712c5cc3ad341be373f Author: jbertram jbert...@apache.org Date: 2015-05-06T19:20:18Z Obey license check property commit 076b56ba9816eb4dee4c6b817ecda8abc7b3654c Author: jbertram jbert...@apache.org Date: 2015-05-06T19:51:31Z Set Arjuna properties commit c9e173e064d0c413d34329c9c9f4180ea13fb5b8 Author: jbertram jbert...@apache.org Date: 2015-05-06T20:04:41Z Use target directory for test data --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: ACTIVEMQ6-96 ensure connectionsAllo...
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/226 ACTIVEMQ6-96 ensure connectionsAllowed work on invm acceptor URI You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/226.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #226 commit 4fa76f600098c3a35dc143d7b7cd2f9229dc4d4a Author: jbertram jbert...@apache.org Date: 2015-05-05T15:39:36Z ACTIVEMQ6-96 ensure connectionsAllowed work on invm acceptor URI --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: License stuff
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/228 License stuff All the example poms needed to be updated so they would use the same location from the license report file (i.e. ratReport.txt). This is necessary so this file can be printed at the end of the Jenkins build so that if the license check fails the developer will know which file caused it. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/228.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #228 commit 26a97dc850be3ae92334e44b8092de5193c43aa3 Author: jbertram jbert...@apache.org Date: 2015-05-05T19:27:32Z Revert disabled RAT plugin by default and updated the docs for releasing explaining how to enable it. This reverts commit d30ffb79c82e513f62b962aa02417e05bf39a204. Reverted because the PR build was missing files without the right license. commit 9dcb2d2faa8026a7c11636a1f72db52d7cb45ec2 Author: jbertram jbert...@apache.org Date: 2015-05-05T21:34:41Z Add license header commit dc78dd4c50b70272675c5c379ef99063446c0c98 Author: jbertram jbert...@apache.org Date: 2015-05-05T21:35:09Z Re-enable refactor license check --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: Initial resource limits + test conf...
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/222 Initial resource limits + test config fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis 70 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/222.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #222 commit 3eb835a8ab86cca7de3848a003dd70c15f0d186d Author: jbertram jbert...@apache.org Date: 2015-05-04T16:15:33Z ACTIVEMQ6-96 acceptor limit Adds a configuration property on both in-vm and Netty acceptors whereby the number of connections allowed is configurable. commit 57d29ed119fe2bdf750911efa02b9eb2966fa260 Author: jbertram jbert...@apache.org Date: 2015-05-04T16:51:55Z Point test configs to right directory commit 46a10c15985b076d5ede0c6e7cbdc234b6a8c824 Author: jbertram jbert...@apache.org Date: 2015-05-04T18:55:14Z ACTIVEMQ6-70 broker resource limits Implements basic limits on the number of connections and number of queues a particular user can create to/on the broker. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-artemis pull request: Rename updates + NPE fix
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/216 Rename updates + NPE fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/216.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #216 commit 791cc5c50c914bfc22dd7adc3fc74e5ff1705929 Author: jbertram jbert...@apache.org Date: 2015-04-29T17:20:31Z More rename updates commit 6af32ca29df17a654d077ede6a0da0815b038fd8 Author: jbertram jbert...@apache.org Date: 2015-04-29T18:35:18Z Avoid potential NPE seen on tests --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Artemis rename
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/213 Artemis rename You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 artemis-rename-new Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/213.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #213 commit f509c075c66a29f112737f3273890bfbc098985f Author: Clebert Suconic clebertsuco...@apache.org Date: 2015-04-27T20:40:36Z ACTIVEMQ6-1 Artemis rename This commit is a simple mv of the files.. We required two commits to preserve history, one to git mv, one for the actual changes... otherwise history would be lost Based on the Apache ActiveMQ community vote this project is being renamed Artemis. commit 8f52a622d0d883ca5e9f60ba7754ed51de38cc5c Author: Justin Bertram jbert...@apache.org Date: 2015-04-27T21:32:30Z ACTIVEMQ6-1 Artemis rename Based on the Apache ActiveMQ community vote this project is being renamed Artemis. commit 9a6ae57d458203e5b18f31b82ff1a625bef96830 Author: jbertram jbert...@redhat.com Date: 2015-04-27T15:24:18Z Casting issue with management op over core commit 08d62dccc05db8144c392ffa5e9944ae48fe945d Author: Clebert clebertsuco...@apache.org Date: 2015-04-27T16:28:34Z ACTIVEMQ6-1 Renaming native and 64/32 bit compilation commit e2e540183300960d5064aaba9f0bc9fd88baeac7 Author: Clebert clebertsuco...@apache.org Date: 2015-04-27T18:45:38Z renaming rdf --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Artemis rename
Github user jbertram closed the pull request at: https://github.com/apache/activemq-6/pull/213 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Artemis rename
GitHub user jbertram reopened a pull request: https://github.com/apache/activemq-6/pull/213 Artemis rename You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 artemis-rename-new Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/213.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #213 commit f509c075c66a29f112737f3273890bfbc098985f Author: Clebert Suconic clebertsuco...@apache.org Date: 2015-04-27T20:40:36Z ACTIVEMQ6-1 Artemis rename This commit is a simple mv of the files.. We required two commits to preserve history, one to git mv, one for the actual changes... otherwise history would be lost Based on the Apache ActiveMQ community vote this project is being renamed Artemis. commit 8f52a622d0d883ca5e9f60ba7754ed51de38cc5c Author: Justin Bertram jbert...@apache.org Date: 2015-04-27T21:32:30Z ACTIVEMQ6-1 Artemis rename Based on the Apache ActiveMQ community vote this project is being renamed Artemis. commit 9a6ae57d458203e5b18f31b82ff1a625bef96830 Author: jbertram jbert...@redhat.com Date: 2015-04-27T15:24:18Z Casting issue with management op over core commit 08d62dccc05db8144c392ffa5e9944ae48fe945d Author: Clebert clebertsuco...@apache.org Date: 2015-04-27T16:28:34Z ACTIVEMQ6-1 Renaming native and 64/32 bit compilation commit e2e540183300960d5064aaba9f0bc9fd88baeac7 Author: Clebert clebertsuco...@apache.org Date: 2015-04-27T18:45:38Z renaming rdf commit 63152b1d4bcb406b7e3f1f1e809d9acbca19b36a Author: Andy Taylor andytay...@apache.org Date: 2015-04-28T09:14:40Z updated images to Artemis --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Renamed ActiveMQ6 to ActiveMQ Artemis
Github user jbertram commented on the pull request: https://github.com/apache/activemq-6/pull/212#issuecomment-95942887 My PR will change the artifact ID, but the group ID will stay the same (i.e. org.apache.activemq) since that is what Apollo uses. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Renamed ActiveMQ6 to ActiveMQ Artemis
Github user jbertram commented on the pull request: https://github.com/apache/activemq-6/pull/212#issuecomment-95943582 I could take Martyn's commit and squash it with mine so it's all together. Would that be preferable? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: ACTIVEMQ6-97 - Change HQ to AMQ for prope...
Github user jbertram commented on the pull request: https://github.com/apache/activemq-6/pull/205#issuecomment-92938159 My understanding is that these properties weren't change due to compatibility with older HornetQ clients. Have you tested these changes with HornetQ clients to ensure there are no regressions? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [DISCUSS} HornetQ ActiveMQ's next generation
I'm not sure I follow you here, Jim. Both Andy and I have labored to clarify the history of the donation. See here http://activemq.2283324.n4.nabble.com/DISCUSS-HornetQ-ActiveMQ-s-next-generation-tp4693781p4693932.html and here http://activemq.2283324.n4.nabble.com/DISCUSS-HornetQ-ActiveMQ-s-next-generation-tp4693781p4693997.html . In my mind, the facts of the matter paint a different picture than the virus analogy you described. Just for clarity's sake, here's a quick review with some additional details to flesh out the timeline a bit: 1) July 8, 2014, discussion is kicked off regarding code donation. See here http://activemq.2283324.n4.nabble.com/Possible-HornetQ-donation-to-ActiveMQ-tp4682971.html . One initial thought is that the donated code would take the mantle of ActiveMQ Apollo to be the next generation of ActiveMQ. 2) The donation is affirmed and welcomed. 3) The community consensus is to place the donated code into a git repository named activemq-6 (or some equivalent). 4) The Git repo https://git-wip-us.apache.org/repos/asf?p=activemq-6.git is created and the donation is committed on October 31, 2014. 5) A JIRA project named ACTIVEMQ6 is created. 6) Jenkins jobs ActiveMQ6-Nightly-Regression-Test and ActiveMQ6-PR-Build are created. 7) GitHub pull-requests are sent and JIRAs are opened providing nearly daily reminders on the dev-list that work on the activemq-6 repository is happening. 8) March 10, first RC of Apache ActiveMQ 6.0.0 is put up for vote. See here http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911.html . RC is voted down mainly due to catX dependency issue. 9) March 12, second RC of Apache ActiveMQ 6.0.0 is put up for vote. See here http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693119.html . RC is voted down due to another catX dependency issue and a few other odds and ends. 10) March 17, third RC of Apache ActiveMQ 6.0.0 is put up for a vote. See here http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693345.html . RC naming is debated a bit. By March 23 consensus seems to be that releases should be suffixed with a -M# to let users know ActiveMQ 6 isn't yet a full replacement for ActiveMQ 5.x. 11) Later on March 23, for the first time to my knowledge broader concerns about the code donation becoming ActiveMQ 6 are raised. The discussion ensues across the whole community on different threads until now. From steps 1-10 (covering over 8 calendar months) there is no clear objection that the donated code-base should not be the basis of the next generation of ActiveMQ. The matter is discussed in the open with lots of community members weighing in. From all I can see, the community consensus was clear (at that time) and the work was done in good faith. Obviously new opinions have come to light over the last week and so the RC vote was cancelled and the discussion is moving forward. Again, the community process is being honored. I don't see how the virus analogy applies or how this could be characterized as a hostile takeover. -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-HornetQ-ActiveMQ-s-next-generation-tp4693781p4694075.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: [DISCUSS} HornetQ ActiveMQ's next generation
Tracy Snell wrote This really should’ve been the first thing the HornetQ camp did when the push back happened. Insisting it should be 6.0 and all the surrounding debate would’ve been greatly reduced had this been the first response. As I read the thread for the original donation it seemed clear to me that the donation was accepted to be a replacement for ActiveMQ Apollo. In other words, the donation would be the basis for the next generation of ActiveMQ. In particular, it would consolidate many of the good things from ActiveMQ 5.x, Apollo, and HornetQ. When it came time to determine where exactly the donation would be placed the consensus was it should be placed in a repository called activemq-6 (or some equivalent). This was suggested and confirmed by people who did not work on the donated code. I believe it was Richard Kettelerij that first suggested this repo name. To be clear, there was a suggestion that the donation might take the Apollo mantle since it was already deemed the next generation of ActiveMQ, but that idea was specifically shot down. ActiveMQ 6 was (at least to me) the clear consensus. I understand that different people understood the donation differently. That's fine. We all have different perspectives. However, I think it's unfair to essentially say that the HornetQ camp insisted on it being called ActiveMQ 6.0. Once the donation was made and stored in https://git-wip-us.apache.org/repos/asf?p=activemq-6.git way back on October 31 a handful of us familiar with the code-base worked in good faith to do what we believed was the consensus (i.e. provide an initial release of ActiveMQ 6). When the first RC of ActiveMQ 6 was cut the release naming was revisited (this thread being a prime example). At that point I think it would have improper for the HornetQ camp to make a blanket decision to rename it. Some in the community understood the donation as I did, and they support it. They want the donation to be ActiveMQ 6. It wouldn't make sense to ignore those community members. Obviously, some understood the donation differently and desire a different name. They shouldn't be ignored either. I feel the resulting discussion (across all the various threads) has been ultimately profitable and, in fact, was the only right way to handle the situation. As I understand it, that is (at least in part) the Apache Way. As I see it, there's been no railroading as you suggested in another post. Has there been misunderstanding and perhaps miscommunication? I'll certainly grant that. Hopefully we're getting that sorted now. -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-HornetQ-ActiveMQ-s-next-generation-tp4693781p4693997.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: [DISCUSS} HornetQ ActiveMQ's next generation
I don't mean to put words into Andy's mouth, but the way I read his post he's saying that before the donation HornetQ had a fair amount of heterogeneity, and now that the donation has occurred there are encouraging signs that the heterogeneity is carrying over into the ActiveMQ community. Clearly there are lines of distinction between those in the ActiveMQ community who are familiar with donated code-base and those that aren't, but (I feel) the community is united in its desire to deliver a quality messaging solution. In general I think that any community with a sufficiently large code-base will have lines of distinction between developers who are familiar with certain areas of the code and those that aren't, but I don't think that necessarily means there are separate communities. I imagine there are already at least a few Apache communities where this is true. -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-HornetQ-ActiveMQ-s-next-generation-tp4693781p4694010.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[GitHub] activemq-6 pull request: Polish and renamed hornetmq to activemq-6
Github user jbertram commented on the pull request: https://github.com/apache/activemq-6/pull/196#issuecomment-86735537 The references to HornetMQ probably weren't caught earlier because nobody thought to search for HornetMQ since the broker's name is HornetQ (without the M). I think that any JIRA links which reference the HORNETQ project should stay as is so historical information remains in-tact. I also think the references in checkstyle.xml are also legit since they reference code used for checkstyle checks. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Log POODLE WARN just once
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/189 Log POODLE WARN just once You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/189.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #189 commit 4a35a6123b6b4e7d007dff2d77f3e4a8e9eab9d8 Author: jbertram jbert...@redhat.com Date: 2015-03-16T19:01:54Z Log POODLE WARN just once --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Clean up @author tags and useless JavaDoc
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/171 Clean up @author tags and useless JavaDoc You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/171.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #171 commit 88ed03e2bdb1f34b4fd94636d5d46e07f756783c Author: jbertram jbert...@redhat.com Date: 2015-03-10T19:28:20Z ACTIVEMQ6-87 Strip @author tags commit fa549a00e737cde0df5fc18b9cb2283561ede017 Author: jbertram jbert...@redhat.com Date: 2015-03-10T19:41:40Z remove useless JavaDoc --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Remove broken links from website
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/156 Remove broken links from website You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/156.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #156 commit 7a3379041e99af510beba3fcf611c3784fa73b9b Author: jbertram jbert...@redhat.com Date: 2015-03-06T19:44:49Z Remove broken links from website --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Handful of fixes
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/146 Handful of fixes You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/146.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #146 commit 9a88941a5138957498f61f996ee5634d936a152e Author: jbertram jbert...@redhat.com Date: 2015-03-04T15:44:43Z ACTIVEMQ6-86 Backup announcement may fail When a live and backup server are both started at or near the same moment there is a small window where the live server's acceptors have been started but the server's state != STARTED. During this window if the backup sends its announcement the announcement will fail and the backup will shutdown. This fix closes this small window by only starting the acceptors until the server is fully started. commit 080c1dd0589346da1b0d50449c02ba2e81ed35c7 Author: jbertram jbert...@redhat.com Date: 2015-03-04T19:11:00Z Make test more robust It is possible for the createHAServerLocator() method to return a connection to the node with the non-default password causing the test to fail. commit 63064506e091d5e622a37a9365e4bc793c6151a1 Author: jbertram jbert...@redhat.com Date: 2015-03-04T19:52:19Z Increase timeouts for slower environments --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: update REST doc
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/124 update REST doc You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/124.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #124 commit c2edaeaac0e15eba68b16aff30e959a66440cd24 Author: jbertram jbert...@redhat.com Date: 2015-02-27T17:02:50Z update REST doc --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Add test for BZ-1193085 just to be safe.
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/106 Add test for BZ-1193085 just to be safe. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/106.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #106 commit 30741395193bf8bf3d57284b823ba1808cdbf178 Author: jbertram jbert...@redhat.com Date: 2015-02-20T21:45:00Z Add test for BZ-1193085 just to be safe. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: repo work
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/99 repo work Remove the reference to the JBoss Maven repo, and make all the necessary adjustments on the child-projects. It turns out we don't even need the security dependencies in the tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_repo_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/99.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #99 commit 4804bbdff8a60eb6774808bcd7ba1e350aa00b16 Author: jbertram jbert...@redhat.com Date: 2015-02-12T15:18:53Z repo work --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: ACTIVEMQ-77 auto queue creation on AMQP s...
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/92 ACTIVEMQ-77 auto queue creation on AMQP send/rec Implements a new feature for the broker whereby it may automatically create and delete queues which are not explicitly defined through the management API or file-based configuration when a client sends a message to or receives from a queue via the AMQP protocol. Note, the destination has to be named like jms.queue.* to be auto- created. The queue may subsequently be deleted when it no longer has any messages and consumers. Auto-creation and auto-deletion can both be turned on/off via address-setting. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/92.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #92 commit 3d62aac9fec0ac299d48b5071e60b6b8184c3a28 Author: jbertram jbert...@redhat.com Date: 2015-02-10T21:18:44Z ACTIVEMQ-77 auto queue creation on AMQP send/rec Implements a new feature for the broker whereby it may automatically create and delete queues which are not explicitly defined through the management API or file-based configuration when a client sends a message to or receives from a queue via the AMQP protocol. Note, the destination has to be named like jms.queue.* to be auto- created. The queue may subsequently be deleted when it no longer has any messages and consumers. Auto-creation and auto-deletion can both be turned on/off via address-setting. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Test fix + STOMP auto-create
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/90 Test fix + STOMP auto-create You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/90.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #90 commit 593ea2dde2d4e8fd6d292b9320de3be254dab1e0 Author: jbertram jbert...@redhat.com Date: 2015-02-03T17:45:47Z test needs more time commit 5c23e8ae89e74ee1f34bcfd8ac72215a356161ef Author: jbertram jbert...@redhat.com Date: 2015-02-03T18:21:09Z ACTIVEMQ6-76 auto queue creation on STOMP send/sub Implements a new feature for the broker whereby it may automatically create and delete queues which are not explicitly defined through the management API or file-based configuration when a client sends a message to or consumes from a queue via the STOMP protocol. Note, the destination has to be named like jms.queue.* to be auto- created. The queue may subsequently be deleted when it no longer has any messages and consumers. Auto-creation and auto-deletion can both be turned on/off via address-setting. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: give receiver a bit more time on bridge t...
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/89 give receiver a bit more time on bridge test This is to address this failure: https://builds.apache.org/job/ActiveMQ6-Nightly-Regression-Test/29/testReport/junit/org.apache.activemq.tests.integration.cluster.bridge/BridgeStartTest/testTargetServerNotAvailableNoReconnectTries_isNetty_true_/. I was able to reproduce the failure locally before the fix, but unable to reproduce the failure (even after several hundred runs) after the fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/89.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #89 commit 20452083d79ef7f6898064556d998cc8ea402e73 Author: jbertram jbert...@redhat.com Date: 2015-02-02T20:59:47Z give receiver a bit more time on bridge test --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: fix potential race condition in test
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/88 fix potential race condition in test this is to address https://builds.apache.org/job/ActiveMQ6-Nightly-Regression-Test/30/testReport/junit/org.apache.activemq.tests.integration.client/SessionTest/testQueueQuery/ You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/88.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #88 commit d523f630a04e68a3da5bbe8692dbf3e58e17c51e Author: jbertram jbert...@redhat.com Date: 2015-02-02T17:51:04Z fix potential race condition in test --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: A few test fixes
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/87 A few test fixes These fixes should help with a few failures seen on https://builds.apache.org/job/ActiveMQ6-Nightly-Regression-Test/27/#showFailuresLink. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/87.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #87 commit 9e214e9c43d32156228c7414bf87cb06b233c7bd Author: jbertram jbert...@redhat.com Date: 2015-01-30T19:34:49Z remove unnecessary cache operation commit fe11fb4c02e3fc0492191224b366df878329e809 Author: jbertram jbert...@redhat.com Date: 2015-01-30T19:35:16Z avoid potential NPE --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: fix tests I broke; refactor a few other p...
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/86 fix tests I broke; refactor a few other pieces You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/86.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #86 commit 5749c7ff94aa82f6bf8b6a79501fc339551e3c5e Author: jbertram jbert...@redhat.com Date: 2015-01-28T22:08:45Z fix tests I broke; refactor a few other pieces --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: fix race in test
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/84 fix race in test You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/84.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #84 commit d895988faf267aa39fe5b37312bd2cbdaa8168f3 Author: jbertram jbert...@redhat.com Date: 2015-01-27T19:29:05Z fix race in test --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Fix test, adjust logging
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/80 Fix test, adjust logging The timeout here needed to be increased to avoid test failure when isNetty=true. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/80.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #80 commit dfb7d3c382382b6e5f0647fb81703931702d0790 Author: jbertram jbert...@redhat.com Date: 2015-01-26T20:03:54Z Fix test, adjust logging --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: removing redundant tests
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/76 removing redundant tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/76.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #76 commit 75bb4d8c95ce520850d86f4996e74df9e72acd02 Author: jbertram jbert...@redhat.com Date: 2015-01-22T18:29:24Z removing redundant tests --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: THIS IS A TEST, DO NOT MERGE
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/75 THIS IS A TEST, DO NOT MERGE You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_bridgeTestFailure Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/75.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #75 commit 8ea21307466d6f6ff38ba891b3c94c37dec2ea8d Author: jbertram jbert...@redhat.com Date: 2015-01-22T16:52:51Z THIS IS A TEST, DO NOT MERGE --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: THIS IS A TEST, DO NOT MERGE
Github user jbertram closed the pull request at: https://github.com/apache/activemq-6/pull/75 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: A few more excludes for RAT plugin
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/70 A few more excludes for RAT plugin These are necessary because for some reason the Apache CI build doesn't recognize all the keystores as binary and it's choking on them. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/70.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #70 commit 5208e768d1790a52d3ad77fa5172d5468f0032fa Author: jbertram jbert...@redhat.com Date: 2015-01-20T16:34:37Z A few more excludes for RAT plugin --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: ACTIVEMQ6-52 Graceful shutdown
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/67 ACTIVEMQ6-52 Graceful shutdown Implements a feature whereby the broker will not shutdown while there are clients connected. A timeout can be specified so that even if there are clients connected the broker will still shutdown after a certain time. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_graceful_shutdown Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/67.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #67 commit dfc039f456f2c239896ebffca96e2baf0e49b5b7 Author: jbertram jbert...@redhat.com Date: 2015-01-19T15:34:09Z ACTIVEMQ6-52 Graceful shutdown Implements a feature whereby the broker will not shutdown while there are clients connected. A timeout can be specified so that even if there are clients connected the broker will still shutdown after a certain time. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: ACTIVEMQ6-13 + pom fix
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/60 ACTIVEMQ6-13 + pom fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_ACTIVEMQ6-13 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/60.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #60 commit 90941f24a156c72a4cfda8a80ecc8c4f9ba59971 Author: jbertram jbert...@redhat.com Date: 2015-01-06T19:34:38Z ACTIVEMQ6-13 auto-create/auto-delete jms queues Implements a new feature for the broker whereby it may automatically create and delete JMS queues which are not explicitly defined through the management API or file-based configuration. A JMS queue is created in response to a sent message or connected consumer. The queue may subsequently be deleted when it no longer has any messages and consumers. Auto-creation and auto-deletion can both be turned on/off via address-setting. commit 92653f664f177b1e978cbbf178300ecdd9acc636 Author: jbertram jbert...@redhat.com Date: 2015-01-12T16:16:00Z Allow snapshots --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Couple of fixes
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/49 Couple of fixes The distribution still needs some work, but this is progress worth committing. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/49.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #49 commit 3080b5806e8249629d3ac12e7d56e6d36cb20d21 Author: jbertram jbert...@redhat.com Date: 2014-12-19T17:51:17Z ACTIVEMQ6-62 Remove unneeded dependency on jackson commit 9322af1d262497316d8c145c8073c49d439ad7bf Author: jbertram jbert...@redhat.com Date: 2014-12-19T22:59:24Z ACTIVEMQ6-11 Fix the distribution build --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: Handful of fixes
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/40 Handful of fixes You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/40.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #40 commit 8b534941b72444568f9e245522cbfab34ea63393 Author: jbertram jbert...@redhat.com Date: 2014-12-05T19:44:14Z ACTIVEMQ6-41 Drop Java EE examples commit 4480687c32e7d89ca684a161ba08c8dbf8079cdc Author: jbertram jbert...@redhat.com Date: 2014-12-05T19:45:19Z ACTIVEMQ6-14 Remove naming from bootstrap commit 53e465a03ba9cceec58f1a815565eead6ed6a8c3 Author: jbertram jbert...@redhat.com Date: 2014-12-05T20:00:49Z ACTIVEMQ6-14 NPE during init commit 8bd25e884442e758ddaa0077a5579143aeda3679 Author: jbertram jbert...@redhat.com Date: 2014-12-09T04:31:39Z ACTIVEMQ6-51 Example server bootstrapping --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] activemq-6 pull request: JNDI implementation change + a few other ...
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/34 JNDI implementation change + a few other fixes Run of the test-suite with these changes: http://messaging-09.jbm.lab.bos.redhat.com:8080/job/activemq6-param/14/#showFailuresLink (all failure appear related to class conflicts between the existing selector implementation and the one from ActiveMQ 5.x used by the OpenWire module). You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-6/pull/34.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #34 commit 1e99dc53a4387fd23c6a547dc2bcb5a1eaaa2573 Author: jbertram jbert...@redhat.com Date: 2014-11-24T22:49:39Z Handful of test fixes commit 540db93400ba9703290a4e4851ffd4022f40f6c1 Author: jbertram jbert...@redhat.com Date: 2014-12-03T14:50:16Z ACTIVEMQ6-14 Replace JNDI server with client impl --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
