Re: [DISCUSS] Adding Derby as a dependency

I can't speak for others on the previous thread, but the below was not my position in that prior discussion at all. I don't think the proposed kafka bridge component should be bundled in the broker repo or distribution, regardless where else the code lives, but that it should instead have its own

Re: [DISCUSS] Adding Derby as a dependency

I'd first wonder if Clebert was talking about pre baked embedded-Derby usage rather than client-server Derby, where it directly creates files on local disk and manages them, i.e. acting somewhat like the journal but giving the option for storage still accessable later via JDBC (though without any

Re: Kafka ServiceConnector

The related PR is https://github.com/apache/activemq-artemis/pull/1607 for anyone not following along thus far, or later reference. My main view there was that such an extension would be better maintained seperate from the main broker repository+distribution for a variety of reasons. After that I

Re: [VOTE] Apache ActiveMQ 5.15.2

On 17 October 2017 at 15:37, Christopher Shannon wrote: > Hi Everyone, > > I have created the ActiveMQ 5.15.2 release and it's ready for a vote. > > The list of resolved issues is here: >

Re: Time for another ASF board report

I've added some initial notes. Robbie On 5 October 2017 at 15:54, Bruce Snyder wrote: > It is time to create a report for the ASF board for October. Please take 5 > minutes and contribute to the report available at the following URL: > >

Re: [RESULT][VOTE] Apache ActiveMQ 5.15.1

On 2 October 2017 at 15:34, Christopher Shannon wrote: > Results of the Apache ActiveMQ 5.15.1 vote: > > Vote passes with 3 +1 binding votes. > > The following votes were received: > > Binding: > +1 Timothy Bish > +1 Christopher Shannon > +1 Clebert Suconic > >

Re: [VOTE] Apache ActiveMQ 5.15.1 #2

On 28 September 2017 at 16:04, Christopher Shannon wrote: > Hi Everyone, > > I have re-created the ActiveMQ 5.15.1 release and it's ready for a vote. > > The list of resolved issues is here: > https://issues.apache.org/jira/secure/ReleaseNote.jspa? >

Re: [VOTE] Apache ActiveMQ 5.15.1

Already mentioned on the JIRAs, but it was actually my recent change on AMQ-6821 rather than Tim's older one on AMQ-6790 that caused that, apologies. I have added the affected feature test to the smoke test profile, i.e. "mvn clean test -Pactivemq.tests-sanity" or "mvn clean test

Re: [DISCUSS] release process improvements

my original script: > > > this print here: > > > echo $theFile > > > > It was a debug statement that I forgot to remove it... I will remove > it from the artemis prepare one. > > > And also, should I keep the download-release.sh on the scripts or should i

Re: [DISCUSS] release process improvements

I've raised https://issues.apache.org/jira/browse/ARTEMIS-1437 with a patch for the website around fixing this and some other issues, plus splitting the older releases out to their own page, if folks could take a look and see what they think. Robbie On 18 September 2017 at 16:58, Robbie Gemmell

Re: [DISCUSS] release process improvements

with details of how to stage the release bits in the dev area before the vote and add them to the release area after it passes. Robbie On 22 September 2017 at 06:00, Clebert Suconic <clebert.suco...@gmail.com> wrote: > +1 > > On Thu, Sep 21, 2017 at 10:09 AM Robbie Gemme

Re: [VOTE] Apache ActiveMQ 5.15.1

On 25 September 2017 at 15:00, Christopher Shannon wrote: > Hi Everyone, > > I have created the ActiveMQ 5.15.1 release and it's ready for a vote. > This release uses the new process based on the discussion from last > week. > > The list of resolved issues is

Re: [DISCUSS] release process improvements

/activemq/artemis/ would similarly improve things further there too, and can do that next if folks are happy. Robbie On 15 September 2017 at 16:55, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > I tweaked the helper script to verify the downloaded tar/zip files > using thei

Re: [DISCUSS] release process improvements

download links to be in > compliance with Apache processes. > >> >> On Sat, Sep 16, 2017 at 6:14 AM, Robbie Gemmell >> <robbie.gemm...@gmail.com> wrote: >>> >>> Yep. I'm not sure exactly how much longer than this it has been the >>> recomm

Re: [DISCUSS] release process improvements

recommendation for > signatures on the official release artifacts is a sha512 based signature, > not the older sha1 that is used in the unofficial maven release artifacts. > > Refer here: > http://www.apache.org/dev/release-distribution.html#sigs-and-sums > > >> >> On

Re: [DISCUSS] release process improvements

t. > > > Feel free to tweak the script. I will be out for a week. I will just > finish the release and I will be away for a week. > > On Thu, Sep 14, 2017 at 5:48 AM Robbie Gemmell <robbie.gemm...@gmail.com> > wrote: > >> Script looks good, though I'd tweak i

Re: [DISCUSS] release process improvements

mentioned extra work.. there's > no extra work here :) > It's actually saving me from screwing up eventually, so I take it as > an improvement. > > > On Wed, Sep 13, 2017 at 1:19 PM, Robbie Gemmell > <robbie.gemm...@gmail.com> wrote: >> Yes, thats essentially

Re: [DISCUSS] release process improvements

the dev repository Robbie is >> mentioning... (that means.. we wouldn't really have an extra step). >> >> >> On thing I'm not sure how to do is... how to upload it to the dev dist >> at https://dist.apache.org/repos/dist/dev/activemq/ >> >> and how we would make

Re: [DISCUSS] release process improvements

On 13 September 2017 at 14:35, Clebert Suconic <clebert.suco...@gmail.com> wrote: > On Wed, Sep 13, 2017 at 9:21 AM Robbie Gemmell <robbie.gemm...@gmail.com> > wrote: > >> This was less about time, though there is some benefit in that regard, >> with how much d

Re: [DISCUSS] release process improvements

> few steps to remember as a release manager and it's easy to make mistakes, > so I would prefer not to change the process unless there's a clear benefit > that warrants it. > > On Wed, Sep 13, 2017 at 10:42 AM, Robbie Gemmell <robbie.gemm...@gmail.com> > wrote: > >

Re: [DISCUSS] release process improvements

pted, but it is still a bit more to do. >>>> >>>> That said, script provided to the reviewer could accomplish the same >>>> things using the current staging location/setup. >>>> >>>> Anyway, I’m -0 to the idea.Getting folks to ac

[DISCUSS] release process improvements

Hi folks, I mentioned on the recent Artemis 2.3.0 vote that I had some suggested changes for the release process improvements, not just for Artemis but for other components too, and would send a mail later. The short version is there are three main things I'd like to suggest as improvements,

Re: [VOTE] Apache ActiveMQ Artemis 2.3.0

On 6 September 2017 at 00:29, Clebert Suconic wrote: > I would like to propose an Apache ActiveMQ Artemis 2.3.0 release, CR2. > > > > We had these new features added as part of 2.3.0: > > [ARTEMIS-1270] - Provide a Management Console for Artemis > [ARTEMIS-1322] - Add a

Re: [DISCUSS] Artemis Docs Page

For releases at Qpid we give each component release its own page that has links to its downloads and docs etc. The main download and documentation pages overview with direct links to current downloads/docs for each componnent, but also link to a page listing prior releases from the previous 2-3

Re: [ANNOUNCE] Logo has been updated

Looks great, though there are a couple of tiny issues. The TM text near the logo is floating a bit out in the middle of nowhere, it should possibly be part of the image itself so others using it pick it up too. The shadowing around the content has a small break in it at the top, may or may not be

Re: [DISCUSS] Single version docs on Artemis

What we do for Qpid is to have a central documentation/download etc page that links to the latest release artifacts and documentation for each component, but then also have specific pages for each component release that includes the artifacts and docs for each specific release. Those are also

Re: [UPDATE] Move of NMS project SVN repositories to Git

Great. Thanks for all the work you've put in to making this happen, I know it was much more involved than expected or it would have been in the past, since it turns out that infra recently stopped doing these migrations on our behalf locally and you instead had to migrate them yourself remotely.

Re: [VOTE] Migrate the NMS Projects from SVN to Git

On 22 February 2017 at 23:25, Timothy Bish wrote: > > Since the discussion around moving the NMS code to Git has died down now > I've decided to just call a vote on the matter. > > The vote covers moving the following NMS projects SVN trees to their own > respective Git

Re: [ANNOUNCE] Apache Artemis 1.5.3 Release

The mirrors take quite a while to sync and its typical to wait a while after putting the files in the dist repo before announcing in order to avoid the 404 errors most folks willcurrently be seeing. Typically I wait 24+hrs to let essentially all of them update, but a significant proportion are

Re: [DISCUSS] Move Apache.NMS project to Git

On 15 February 2017 at 23:41, Jim Gomes wrote: > Breaking this out into its own discussion thread... > > It has been proposed that Apache.NMS Subversion repository be moved to a > Git repository. While the dominate reason seems to be "that's what > everyone else is doing", I'm

Re: [DISCUSS] Rework NMS.AMQP

On 14 February 2017 at 19:32, Duane Pauls wrote: > Hello, > > I'm relatively new to the ActiveMQ community, but I've been watching this > list for the last little while and would like to propose some rework to the > NMS.AMQP API. > > I'm interested in any feedback you folks

Re: [DISCUSS] ActiveMQ utility project name

If you really need a bridge for what you think then we need the project as > suggested. > > > On Wed, Feb 1, 2017 at 12:47 PM Robbie Gemmell <robbie.gemm...@gmail.com> > wrote: > >> I would echo Tim's comments, particularly around test client code. I'm >> in th

Re: [DISCUSS] ActiveMQ utility project name

I would echo Tim's comments, particularly around test client code. I'm in the middle of seperating things elsewhere that probably shouldn't have been lumped together initially. Beyond that, the first thing infra will likely tell folks to do is to use http://reporeq.apache.org for any new

Re: [DISCUSS] Web site update

The content for most of the site is actually a Confluence wiki, which is converted into the HTML pages for the website, with those then being committed into an svn repo, and that being mirrored onto the webservers upon commit by an svnpubsub process. The 'source' for the website is mostly:

Re: [DISCUSS] distribute binary in .deb and .rpm

I know the infra team and some projects have some hosting on bintray (https://bintray.com/apache/), and that can host .deb and .rpm. Whether its used by projects to do that, and what any process around that would be if they do, I'm not sure. Perhaps worth asking infra. On 12 December 2016 at

Re: [DISCUSS] LevelDB deprecation

Seems like a good idea to me. On 15 November 2016 at 11:45, Christopher Shannon wrote: > Hi Everyone, > > I just wanted to ask what people think about officially deprecating LevelDB > in our 5.x broker and update our documentation to say that it is no longer >

Re: [DISCUSS] removing aerogear / vertx module

On 28 October 2016 at 05:56, Clebert Suconic wrote: > There are a few modules on Artemis that I feel are a bit defunct. I > don't really think anyone will be using it: > > - aerogear: > * It's not working > * I am not sure about the status of Aerogear > *

Re: Unsubscribe issue.

The details are readily available on the website, at http://activemq.apache.org/mailing-lists.html as various folks have mentioned in earlier replies. The unsubscribe addresses are of the form -unsubscribe@, so for example in this case as listed on the website they would be:

Re: [VOTE]Apache ActiveMQ 5.14.1 #2

On 27 September 2016 at 18:40, Christopher Shannon wrote: > Hi Everyone, > > I have re-created the ActiveMQ 5.14.1 release and it's ready for a vote. > > The list of resolved issues is here: > https://issues.apache.org/jira/secure/ReleaseNote.jspa? >

Re: [ANNOUNCE] Apache Artemis 1.4.0 Released

Adding the right dev@ list back to the recipients this time...read on below, if you didnt see it elsewhere already ;) On 13 September 2016 at 22:59, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > The mirrors just replicate whatever is on the main dist repo. They > take a var

Re: [VOTE] Apache ActiveMQ 5.14.0

+1 (non-binding) I gave things a check out by doing the following: - Verified the signatures. - Checked for licence + notice files being present. - Ran the source build (only, no tests). - Started the broker from the tar.gz binary, ran some AMQP client examples against it. - Used the staged maven

Re: [VOTE] Apache ActiveMQ 5.13.4

On 14 July 2016 at 16:46, Christopher Shannon wrote: > Hi Everyone, > > I have created the ActiveMQ 5.13.4 release and it's ready for a vote. This > release has almost 30 bug fixes and improvements. > > The list of resolved issues is here: >

Re: RAT Checks get stuck on Artemis Integration Test Module

Changing to the -n option to -f gives a preview listing of what would be deleted. You can use -e flags to prevent deleting certain things, like any IDE config dirs. On 5 July 2016 at 00:26, John D. Ament wrote: > Doing a git clean fixed it. But last time I blindly run a

Re: [VOTE] Apache Artemis 1.3.0

On 9 June 2016 at 14:03, Martyn Taylor wrote: > Hello all, > > I'd like to propose an Apache Artemis 1.3.0 release. > > Since 1.2.0 we've had a lot of fixes and improvements: > > * The OpenWire protocol implementation is now feature complete. > * Equivalent implementations of

missing svngit2jira JIRA commit updates

Hi all, I've raised https://issues.apache.org/jira/browse/INFRA-11842 regarding the svngit2jira bot failing to post updates to various (but not all) JIRAs/projects, infra are looking into it. Robbie

Re: 5.12.2 version still unreleased in JIRA

Great, thanks. On 22 February 2016 at 12:25, Christopher Shannon <christopher.l.shan...@gmail.com> wrote: > I updated JIRA and released 5.12.2, 5.12.3, and 5.11.4. > > On Mon, Feb 22, 2016 at 6:35 AM, Robbie Gemmell <robbie.gemm...@gmail.com> > wrote: > >> The 5

5.12.2 version still unreleased in JIRA

The 5.12.2 version is still unreleased in JIRA, can someone with permissions update it? Robbie

Re: [VOTE] Release ActiveMQ-CPP v3.9.2

On 3 February 2016 at 14:57, Timothy Bish wrote: > New vote open for ActiveMQ-CPP v3.9.2 > > This is a new patch release of the ActiveMQ-CPP client with a fix for > how the STOMP protocol handlers deal with composite destinations. > > The source bundles for this release can

Re: [VOTE] Apache ActiveMQ 5.13.1

+1 (non-binding) Verified the signature files, ran the source build, ran some of the tests, used the staged maven artifacts with the Qpid JMS master build and tests, kicked the tyres on the binary release with the Qpid JMS HelloWorld example. Robbie On 2 February 2016 at 18:34, Christopher

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

at 12:43 PM, Timothy Bish <tabish...@gmail.com> wrote: >>> On 01/20/2016 11:43 AM, Robbie Gemmell wrote: >>>> On 20 January 2016 at 15:16, Timothy Bish <tabish...@gmail.com> wrote: >>>>> On 01/20/2016 07:26 AM, Christopher Shannon wrote: >>

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

(that I'm not entirely sure how successfully came to actually get in there again) to be cleared out. Robbie On 26 January 2016 at 10:15, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > Infra have now blown the repo contents away. The ActiveMQ 5 deploy job > has run to publish

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

Suconic <clebert.suco...@gmail.com> wrote: > 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 > <robbie.gem

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

4.0-SNAPSHOT if no one has any >>> complaints. >>> >>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <tabish...@gmail.com> wrote: >>> >>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote: >>>> > On 18 January 2016 at 18:46, Rob

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

gt; I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any >> complaints. >> >> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <tabish...@gmail.com> wrote: >> >>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote: >>>> On 18 Jan

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

On 18 January 2016 at 18:46, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > On 18 January 2016 at 15:53, Timothy Bish <tabish...@gmail.com> wrote: >> We seem to have a bit of a mess in our snapshots area with lots of old >> snapshots for ancient releases like 5.3, 5.

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

On 18 January 2016 at 15:53, Timothy Bish wrote: > We seem to have a bit of a mess in our snapshots area with lots of old > snapshots for ancient releases like 5.3, 5.4, etc along with snapshots > for an ActiveMQ 6.0.0 release that has caused some confusion recently. > > Some

Re: [VOTE] Apache ActiveMQ 5.12.2 #3

On 5 January 2016 at 16:18, Christopher Shannon wrote: > Hello everyone, > > The problem with AMQ-6094 has been fixed I have re-created the ActiveMQ > 5.12.2 release and it's ready for a vote. This release has over 25 bug > fixes and improvements. > > The list of

Re: [VOTE] Apache ActiveMQ 5.12.2 #2

On 16 December 2015 at 15:48, Christopher Shannon wrote: > Hello everyone, > > The problem with the previous release attempt has been fixed I have > re-created the ActiveMQ 5.12.2 release and it's ready for a vote. This > release has 20 bug fixes and >

Re: [VOTE] Apache ActiveMQ 5.13.0

On 30 November 2015 at 14:22, Christopher Shannon wrote: > Hello everyone, > > I have cut the ActiveMQ 5.13.0 release and it's ready for a vote. This > release has over 80 bug fixes and new features. > > The list of resolved issues is here: >

Re: ActiveMQ does not seem to honor the agreed upon idle-time-out

On 22 October 2015 at 17:21, mbroadst wrote: > Hi Tim, > Okay, I'm going by section 2.4.5 of the spec here where it indicates: "At > connection open each peer communicates the maximum period between activity > (frames) on the connection that it desires from its partner." Then

Re: [VOTE] Apache ActiveMQ 5.12.1

On 12 October 2015 at 19:33, Christopher Shannon wrote: > Hello everyone, > > I have cut the ActiveMQ 5.12.1 release and it's ready for a vote. This > release has 22 bug fixes and > improvements. > > The list of resolved issues is here: >

Re: [VOTE] Release Apache.NMS API 1.7.1

I'm not currently fixed to build/try the bits and my vote is non-binding anyway (seems you now have the requried number though), but I gave the artifacts a quick look at. I checked they had licence+notice files and the sigs verified, which they did, though the Apache.NMS-1.7.1-bin.src.asc sig

Re: [RESULT] [VOTE] Release Qpid JMS client 0.5.0

..and to include the correct dev@ list... ;) On 31 August 2015 at 13:40, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > There were 4 binding +1 votes, and no other votes received. The vote has > passed. > > I will add the archives to the dist release repo and release the ma

Re: [HEADS-UP/Discussion] Artemis: Planning a release soon

Yeah I think 1.1.0 fits better too, both for whats actually in it now and also for a future approach like Claus mentioned. Robbie On 13 August 2015 at 08:53, Claus Ibsen claus.ib...@gmail.com wrote: Hi I think 1.1.0 is better. Maybe here in the start where more new functions is added /

Re: [VOTE] Apache ActiveMQ 5.12.0

On 10 August 2015 at 19:11, Timothy Bish tabish...@gmail.com wrote: Hi folks, I've just cut a release candidate for the ActiveMQ 5.12.0 release and it's ready for a vote. This release has 180+ bug fixes and improvements. A large amount of work has gone into hardening the AMQP and MQTT

Re: [VOTE] Apache ActiveMQ 5.12.0

I haven't yet had an oportunity to test the artifacts, but I'll vote once I have. I'm not sure I see that the release is being rushed really. 5.12 has been 'coming soon' for a reasonable while now, and folks have mentioned that on both the lists recently. Tim and Dan both sent out a headsup mails

Re: [DISCUSS] Artemis Coding Style

On 4 August 2015 at 12:56, Christopher Shannon christopher.l.shan...@gmail.com wrote: So in general I'm not too picky with coding styles but I just started looking at the Artemis project a few days ago and something that stood out to me right away was the use of opening curly braces on a new

Re: constant updating of the Unix Shell Script website page

can i find it? Regards Marc Am 29.07.2015 um 18:12 schrieb Robbie Gemmell: Hi folks, The Unix Shell Script page (http://activemq.apache.org/unix-shell-script.html) seems to be driving the website Buildbot a bit nuts. It commits an update for this page every hour and mails the commits

Re: constant updating of the Unix Shell Script website page

to have fixed it. It SHOULD just be rendering the pages that have changed. Dan On Aug 3, 2015, at 5:45 AM, Robbie Gemmell robbie.gemm...@gmail.com wrote: I don't know what the current export process used is or where it is running exactly, other than the commit emails giving away

constant updating of the Unix Shell Script website page

Hi folks, The Unix Shell Script page (http://activemq.apache.org/unix-shell-script.html) seems to be driving the website Buildbot a bit nuts. It commits an update for this page every hour and mails the commits@ list. It looks like the Table of Contents could be the issue. It seems to be changing

Re: qpid cpp text message

On 15 July 2015 at 20:51, plsph gf...@wp.pl wrote: it was typo during rewrite. broker settings are fine. i don't know what the consumer is. i only got producer and broker. it's hard to argue with statement that it should work. i've used qpid-proton writen in c and i was able to send messages

Re: qpid cpp text message

On 14 July 2015 at 13:52, plsph gf...@wp.pl wrote: it still gives BytesMessage probably, the problem is with: If the transformer is set to 'jms', the they type of JMS message will depend on the body type of the AMQP message. Body Type JMS Message Type null

Re: qpid cpp text message

You dont actually seem to be calling setContentObject at all in the snippet below, but look to be constructing it with it. Did you try setting the content using setContentObject instead? My take from reading previous posts on the subject (such as the one linked previously, by the person who wrote

Re: [DISCUSS] enabling svngit2jira integration?

On 7 July 2015 at 18:33, Timothy Bish tabish...@gmail.com wrote: Hey, awhile back Robbie brought this up on the dev list but it didn't get much attention so I thought I'd bring it up and see if anyone had any issues with us asking infra to enable the svngit2jira bit on our various repos? If

Re: qpid cpp text message

On 9 July 2015 at 14:23, Timothy Bish tabish...@gmail.com wrote: On 07/09/2015 04:40 AM, plsph wrote: hi when sending message by qpid proton writen in c, by default the message is text message and i can recieve it with amqp broker in jms format, but when i try to send message by qpid-cpp

Re: Artemis and Eclipse...

Do you mean the -Xdoclint:none option? Javadoc is stricter with Java8 and will refuse to process things that 'worked' with Java7. You can make it lenient again using the -Xdoclint config option, but that only works when using Java8 and so setting it then makes javadoc processing fail when building

Re: [DISCUSSION] License Headers on Artemis/package-info.java

Yes thats what I do on all .java files, I'm not actually sure why we would put the header as a Javadoc. We dont particularly want it to show up visibly on the resulting documentation (and it isnt strictly required on generated files, only their source), and there isnt anything in there which we

Re: [DISCUSSION] Renaming github mirror

:16, Clebert Suconic clebert.suco...@gmail.com wrote: too late :) On Thu, May 21, 2015 at 7:53 PM, Robbie Gemmell robbie.gemm...@gmail.com wrote: Err, I'd maybe hold up until tomorrow and give other folks a chance to chime in, the below was only one persons opinion hehe. When I say 'now' vs

Re: [DISCUSSION] Renaming github mirror

Infra have updated the 3 repos/mirrors so they now say ActiveMQ Artemis. Robbie On 22 May 2015 at 09:20, Robbie Gemmell robbie.gemm...@gmail.com wrote: The GitHub mirror has been recreated, and now correctly says it is mirroring from the git://git.apache.org/activemq-artemis.git asf mirror

Re: [VOTE] Apache Artemis 1.0.0 (RC3)

+1 (non-binding) I tested out the src+bin tar.gz archives: - Verified the sigs - Checked that the license/notice files are present and look ok. - Built the src archive, ran the tests from the fast-tests profile. - Followed the README in the binary archive to configure and start the broker. -

Re: [DISCUSSION] Renaming github mirror

rather new to Apache and the open source community, so I’m a little confused. When you say “Infra”, what exactly are you referring to? Is this a part of the Apache team? Thanks On May 22, 2015, at 7:52 AM, Robbie Gemmell robbie.gemm...@gmail.com wrote: Infra have updated the 3 repos/mirrors

Re: [DISCUSSION] Renaming github mirror

As the JIRA project has just been renamed today and no release has occurred yet, I think now would probably be the best time to ever recreate the mirror. I dont think the pull requests numbers beginning again is that big an issue. The comments are available on the dev list as you said, and also

Re: [VOTE] Apache Artemis 1.0.0 (RC2)

On 13 May 2015 at 18:12, Martyn Taylor mtay...@redhat.com wrote: Hello all. I've cut a second release candidate of Apache Artemis 1.0.0 addressing the initial RC feedback from community members. This is a first release of the Artemis project with protocol support for AMQP, STOMP, CORE,

[jira] [Updated] (AMQ-5699) AMQP: Update to released Proton-J 0.9

[ https://issues.apache.org/jira/browse/AMQ-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated AMQ-5699: Attachment: AMQ-5699.patch Attaching patch used to try out the current 0.9.1 branch (built locally

[jira] [Comment Edited] (AMQ-5699) AMQP: Update to released Proton-J 0.9

[ https://issues.apache.org/jira/browse/AMQ-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14514426#comment-14514426 ] Robbie Gemmell edited comment on AMQ-5699 at 4/27/15 4:51 PM

[jira] [Commented] (AMQ-5699) AMQP: Update to released Proton-J 0.9

[ https://issues.apache.org/jira/browse/AMQ-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14514423#comment-14514423 ] Robbie Gemmell commented on AMQ-5699: - In trying this Tim spotted an issue with 0.9

Re: [IMPORTANT][HEADS-UP] Renaming trunk to master

) Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Tue, Jan 6, 2015 at 1:44 PM, Robbie Gemmell robbie.gemm...@gmail.com wrote: +1 for the rename. Using master

[jira] [Commented] (AMQ-5503) Make init script more reliable

[ https://issues.apache.org/jira/browse/AMQ-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14510784#comment-14510784 ] Robbie Gemmell commented on AMQ-5503: - Hi Marc, I havent looked at your changes, but I

[jira] [Commented] (AMQ-5738) AMQP memory leak of sender links while closing non-durable consumers

[ https://issues.apache.org/jira/browse/AMQ-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14506721#comment-14506721 ] Robbie Gemmell commented on AMQ-5738: - I noticed this while investigating memory leaks

[jira] [Commented] (AMQ-5738) AMQP memory leak of sender links while closing non-durable consumers

[ https://issues.apache.org/jira/browse/AMQ-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14506720#comment-14506720 ] Robbie Gemmell commented on AMQ-5738: - Fixed in https://git-wip-us.apache.org/repos/asf

[jira] [Resolved] (AMQ-5738) AMQP memory leak of sender links while closing non-durable consumers

[ https://issues.apache.org/jira/browse/AMQ-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved AMQ-5738. - Resolution: Fixed AMQP memory leak of sender links while closing non-durable consumers

[jira] [Created] (AMQ-5738) AMQP memory leak of sender links while closing non-durable consumers

Robbie Gemmell created AMQ-5738: --- Summary: AMQP memory leak of sender links while closing non-durable consumers Key: AMQ-5738 URL: https://issues.apache.org/jira/browse/AMQ-5738 Project: ActiveMQ

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)

+1 (non-binding) I tested out the src+bin tar.gz archives as follows: - Checked the license/notice files were present and look ok. - Verified the sigs using key from https://people.apache.org/keys/committer/martyntaylor.asc - Checked the deps in the binary tar look good license wise. - Built the

[jira] [Resolved] (AMQ-5559) AMQP: dont list filters which are not actually being applied in AMQP attach responses

[ https://issues.apache.org/jira/browse/AMQ-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved AMQ-5559. - Resolution: Fixed Looks good to me, resolving. We could optimise out the empty filter array

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC2)

of explicit policy. What is an apache release may indeed, in the future, extend to what is in maven, and we will be ahead of the curve with the inclusion of these two files :-) [1] http://www.apache.org/dev/release.html#where-do-releases-go On 13 March 2015 at 16:15, Robbie Gemmell robbie.gemm

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC2)

I downloaded the src+bin tar.gz files, and gave the src build a run through and kicked the tyres on the binary. The NPE from RC1 when using an AMQP client is now fixed. In the docs the links to the configuration index now work, and the table there now links to the .html files rather than the .md

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC2)

at the licenses.. thanks again! On Fri, Mar 13, 2015 at 11:16 AM, Robbie Gemmell robbie.gemm...@gmail.com wrote: I downloaded the src+bin tar.gz files, and gave the src build a run through and kicked the tyres on the binary. The NPE from RC1 when using an AMQP client is now fixed. In the docs

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC2)

On 13 March 2015 at 15:59, Martyn Taylor mtay...@redhat.com wrote: On 13/03/15 15:16, Robbie Gemmell wrote: I downloaded the src+bin tar.gz files, and gave the src build a run through and kicked the tyres on the binary. The NPE from RC1 when using an AMQP client is now fixed. In the docs

[jira] [Resolved] (ACTIVEMQ6-55) lack of link context when processing AMQP detach response results in NPE

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ACTIVEMQ6-55. - Resolution: Fixed Fix Version/s: 6.0.0 Resolving this as the PR was merged. I

[jira] [Resolved] (ACTIVEMQ6-58) unable to authenticate with an AMQP client using SASL

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ACTIVEMQ6-58. - Resolution: Fixed This shas been fixed by other changes made since raising the issue

<    1   2   3   4   5   6   7   >