Github user pgfox commented on the issue:
https://github.com/apache/activemq-artemis/pull/1696
- added in @michaelandrepearce commit to the PR
- fixed a few minor check style infringements
- added testing to exercise some of the sorting code
I did not squash the commi
Github user andytaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/1644
@mtaylor are we ok merging this?
---
Github user RaiSaurabh commented on the issue:
https://github.com/apache/activemq-artemis/pull/1696
Thanks, @michaelandrepearce @pgfox for the details provided I will keep
this in mind for future.
---
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1688
@stanlyDoge good work :) +1, will look to merge later today if no one else
does before me.
---
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1684
@RaiSaurabh seems you've reverted this, are you working on an alternative
solution? Is it worth closing this PR till ready?
---
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1697
@stanlyDoge is this ready? If so could you squash the commits into one?
---
Github user RaiSaurabh commented on the issue:
https://github.com/apache/activemq-artemis/pull/1684
@michaelandrepearce I have taken your suggestion and implemented it.
Currently, I am testing it will push it in a day or two. I am ensuring that all
the headers are retained on conversi
Github user stanlyDoge commented on the issue:
https://github.com/apache/activemq-artemis/pull/1697
@michaelandrepearce Yes, it should be ready.
---
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1696
@mtaylor Ill look to merge this later today, if you wanted to check it
before hand?
---
Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/1696
@pgfox @michaelandrepearce This looks reasonable to me. Nice work on
catching these issues.
---
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/1696
---
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/1688
---
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1696
@pgfox all merged now, thanks for this!
---
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1688
@stanlyDoge all merged, thanks for this.
---
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1697
@stanlyDoge unfortunately it seems there is a build failure of this PR,
could you look at it?
---
Github user jdanekrh commented on the issue:
https://github.com/apache/activemq-artemis/pull/1688
wow!
such fix!
thanks much!
---
Github user pgfox commented on the issue:
https://github.com/apache/activemq-artemis/pull/1696
Thanks @michaelandrepearce , @mtaylor
---
Github user stanlyDoge commented on the issue:
https://github.com/apache/activemq-artemis/pull/1697
Oops with squashing. Should be ok now, let's wait for check.
---
GitHub user gtully opened a pull request:
https://github.com/apache/activemq-artemis/pull/1703
[ARTEMIS-1552] ensure gssapi sasl mech can deal with empty receive buâ¦
â¦ffer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gtully
Hello Guys,
How can messages be distributed among subscribers of a queue ? I have a
customer-support chat scenario using activemq where multiple customers can
chat with multiple support representatives. Customer can use a static queue
or temporary queues for listening. But how can we distribute ch
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/1690
---
I wanted to emphasize an idea I spoke here:
Instead of converting the AMQ5 docs back into website format.. I think
it would be great to have the docs into a MD format so it would be
just a like a documentation format. gitbook convertible.
is there a requirement to keep the docs as website? we c
JMS queues automatically load share across consumers. Make sure to set
prefetch size to 1 to get the level of fairness in distribution that you'll
want for this use-case.
For the chat portion, have you looked at a chat-based solution? The
messaging for chat is a specific pattern - point-to-point
I agree, gitbook or similar would be a great way to manage the docs for 5.x.
@Bruce any luck with the extract of the current bits so can play around ?
Sent from my iPhone
> On 12 Dec 2017, at 16:19, Clebert Suconic wrote:
>
> I wanted to emphasize an idea I spoke here:
>
>
> Instead of conv
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/1704
ARTEMIS-1553 JSON values all being converted to String
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ART
we would need to keep the current ones hidden somewhere.. these links
are 10+ years old.. it would break anyone referring linked docs. Think
of your customers with bookmarks.
@Bruce: WDYT?
On Tue, Dec 12, 2017 at 11:46 AM, Michael André Pearce
wrote:
> I agree, gitbook or similar would be a grea
On Tue, Dec 12, 2017 at 4:46 PM, Michael André Pearce <
michael.andre.pea...@me.com> wrote:
> I agree, gitbook or similar would be a great way to manage the docs for
> 5.x.
>
Exporting to MD and creating a gitbook seems like a big task, I suspect any
tool we use will cause a bunch of styling/conte
> Exporting to MD and creating a gitbook seems like a big task, I suspect any
> tool we use will cause a bunch of styling/content issues.
>
> At least initially, how about we just create a nice landing page that
> brings the ActiveMQ site and Artemis site together, and refresh/align the
> existing
What’s 1600 pages between friends
I agree it will be easier to covert to md than to start doing css styles. It’s
all from a wiki anyhow so it’s can’t be that far off.
It be good to get some samples (eg 50 pages) if not all just to try and see
what it is like.
On 12 Dec 2017, at 17:04,
Id be happy to spend some time helping
On 12 December 2017 at 17:30, Michael André Pearce <
michael.andre.pea...@me.com> wrote:
> What’s 1600 pages between friends
>
> I agree it will be easier to covert to md than to start doing css styles.
> It’s all from a wiki anyhow so it’s can’t be that
I was thinking there would be a single css file for all the pages. But I
haven't seen the files yet. Let's have a play around when Bruce pushes the
export.
Cheers
On 12 Dec 2017 5:30 pm, "Michael André Pearce"
wrote:
> What’s 1600 pages between friends
>
> I agree it will be easier to cove
I'm going to address all the questions to me in this single reply.
My original suggestion was that we export the HTML from Confluence, convert
to Markdown and put the Markdown and the images in a git repo. Markdown is
much easier to edit than raw HTML, especially the HTML exported from
Confluence
I had the following empty git repo created to hold the HTML from the
current website:
https://github.com/apache/activemq-web
However, I have a conundrum -- content cannot be pushed directly to a
Github ASF repo. Content can only be added via pull request but Github does
not allow a pull request o
33 matches
Mail list logo
