[GitHub] activemq-artemis pull request: Fix for ARTEMIS-362

GitHub user l-dobrev opened a pull request: https://github.com/apache/activemq-artemis/pull/348 Fix for ARTEMIS-362 Fix for https://issues.apache.org/jira/browse/ARTEMIS-362 You can merge this pull request into a Git repository by running: $ git pull

Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft

Infra have now blown the repo contents away. The ActiveMQ 5 deploy job has run to publish a new 5.14.0-SNAPSHOT. The nightly Artemis deploy job failed because the build seems to reference some of the older snapshot artifacts that got deleted:

[GitHub] activemq-artemis pull request: ARTEMIS-357 fixing an issue created...

GitHub user clebertsuconic opened a pull request: https://github.com/apache/activemq-artemis/pull/350 ARTEMIS-357 fixing an issue created by my previous commit on this @jbertram helped figuring out the growing buffer issue You can merge this pull request into a Git repository by

[GitHub] activemq-artemis pull request: ARTEMIS-357 fixing an issue created...

Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-artemis/pull/350#issuecomment-175383216 Tests are broken though.. will have to look tomorrow --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] activemq-artemis pull request: ARTEMIS-357 fixing an issue created...

Github user jbertram commented on the pull request: https://github.com/apache/activemq-artemis/pull/350#issuecomment-175378662 Nice work, @clebertsuconic. Glad we squashed this bug. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] activemq-artemis pull request: ARTEMIS-357 fixing an issue created...

Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-artemis/pull/350#issuecomment-175393266 fixed the 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

[GitHub] activemq-artemis pull request: Update to current 'artemis help cre...

GitHub user paulgallagher75 opened a pull request: https://github.com/apache/activemq-artemis/pull/349 Update to current 'artemis help create' synopsis and extra console ou… …tput when running 'artemis create' You can merge this pull request into a Git repository by running:

[GitHub] activemq-artemis pull request: Fix for ARTEMIS-362

Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-artemis/pull/348#issuecomment-175096224 I would like to see a description on the commit about what is being changed... It's fairly common having to do a git log to figure out when

[GitHub] activemq-artemis pull request: Fix for ARTEMIS-362

Github user l-dobrev commented on the pull request: https://github.com/apache/activemq-artemis/pull/348#issuecomment-17508 Amended. How's that? --- 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

[GitHub] activemq-artemis pull request: Fix for ARTEMIS-362

Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-artemis/pull/348#issuecomment-175112492 much better.. thanks --- 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

[GitHub] activemq-artemis pull request: Fix for ARTEMIS-362

Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-artemis/pull/348#issuecomment-175148138 It seems nice and clear to be merged.. but I am running the entire testsuite on my box before merging this.. .just to be safe. --- If your project is

Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft

I ran the Artemis job again after Clebert fixed the example poms (thanks!), so the updated 1.3.0-SNAPSHOT files for Artemis are now in place: https://builds.apache.org/view/A-D/view/ActiveMQ/job/Artemis-deploy/71/ I've updated the INFRA ticket asking for the couple of stale 1.1.1-SNAPSHOT bits

[GitHub] activemq-artemis pull request: Fix for ARTEMIS-362

Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/348 --- 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

[GitHub] activemq-artemis pull request: Use waitDisconnect more

Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/347 --- 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

Re : Devis Référencement Google

Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft

I had a mistake on a few examples.. and for some weird error 70 succeeded creating the 1.1.1 that you probably saw? It's fixed now, and it shouldn't happen again. On Tue, Jan 26, 2016 at 2:40 PM, Robbie Gemmell wrote: > I ran the Artemis job again after Clebert fixed

Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft

Yeah, I can only think that for build #70 the required old 1.1.1-SNAPSHOT bits being referenced were still in the local repo on that node from a previous build which let it work, but werent where #69 ran so it failed. Shouldnt be an issue going forward. On 26 January 2016 at 23:04, Clebert

Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft

On 01/26/2016 06:17 PM, Robbie Gemmell wrote: > Yeah, I can only think that for build #70 the required old > 1.1.1-SNAPSHOT bits being referenced were still in the local repo on > that node from a previous build which let it work, but werent where > #69 ran so it failed. Shouldnt be an issue going

[GitHub] activemq-artemis pull request: Update to current 'artemis help cre...

Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/349 --- 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