[
https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14102871#comment-14102871
]
Jim Gomes commented on AMQNET-454:
--
Applied Patch #30, and modified the vendor
[
https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14094851#comment-14094851
]
Jim Gomes commented on AMQNET-454:
--
I refactored Patch 27 to preserve the standard nant
[
https://issues.apache.org/jira/browse/AMQNET-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-486.
--
Resolution: Fixed
NAnt scripts clean target is too aggressive
Jim Gomes created AMQNET-486:
Summary: NAnt scripts clean target is too aggressive
Key: AMQNET-486
URL: https://issues.apache.org/jira/browse/AMQNET-486
Project: ActiveMQ .Net
Issue Type: Bug
+1
On Wed, Jul 16, 2014 at 3:34 PM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.3
This is a bug fix only release focusing on some issues with Consumers in
local transacted sessions and an update to the ZLib library to
+1
On Thu, Jun 5, 2014 at 7:08 AM, Dejan Bosanac de...@nighttale.net wrote:
Hi folks,
I've just cut a second release candidate for the 5.10.0 release. This
release has
232 bug fixes and improvements.
Could you review the artifacts and vote?
The list of resolved issues is here:
[
https://issues.apache.org/jira/browse/AMQNET-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-478.
--
Resolution: Fixed
Port the ignoreExpiration option from Apache.NMS.ActiveMQ to Apache.NMS.Stomp
[
https://issues.apache.org/jira/browse/AMQNET-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-477.
--
Resolution: Fixed
Added new vs2013 solutions and android projects. No code changes necessary.
Port
[
https://issues.apache.org/jira/browse/AMQNET-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007517#comment-14007517
]
Jim Gomes commented on AMQNET-464:
--
Would it make more sense to create a new REST
[
https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-327:
-
Description:
The solution files should be upgraded to VisualStudio 2013. At the same time,
now
Jim Gomes created AMQNET-477:
Summary: Port the NMS library, Stomp and MQTT providers to Xamarin
Android
Key: AMQNET-477
URL: https://issues.apache.org/jira/browse/AMQNET-477
Project: ActiveMQ .Net
[
https://issues.apache.org/jira/browse/AMQNET-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-477:
-
Component/s: MQTT
Port the NMS library, Stomp and MQTT providers to Xamarin Android
Jim Gomes created AMQNET-478:
Summary: Port the ignoreExpiration option from Apache.NMS.ActiveMQ
to Apache.NMS.Stomp
Key: AMQNET-478
URL: https://issues.apache.org/jira/browse/AMQNET-478
Project
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-338:
-
Fix Version/s: 1.6.0
1.6.3
Merged fix for NMS.ActiveMQ into the 1.6.x branch
I merged the fix into the NMS.ActiveMQ 1.6.x branch, so it will be included
in the NMS.ActiveMQ 1.6.3 version. The NMS.Stomp 1.6.x branch was made
after the fix was made in its trunk version, so the fix will be included in
the NMS.Stomp 1.6.0 version.
On Mon, Apr 21, 2014 at 12:08 AM, Jim Gomes
30 seconds. I read
the message wrote by Jim Gomes at 10/Apr/14:
Resolving the issue based on previous check-in fix and said it already
fix in version 1.7.
But I find the newest version in the activemq website is 1.6.2, How can
I find version 1.7? or when is the version 1.7 release?
If I
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-338.
--
Resolution: Fixed
Fix Version/s: (was: 1.6.3)
(was: 1.6.1)
Resolving
[
https://issues.apache.org/jira/browse/AMQNET-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-475:
-
Description:
The implementation of the internal DoCreateMessageProducer() does not use the
passed
Jim Gomes created AMQNET-475:
Summary: Session.DoCreateMessageProducer() does not use the passed
in ProducerId
Key: AMQNET-475
URL: https://issues.apache.org/jira/browse/AMQNET-475
Project: ActiveMQ .Net
[
https://issues.apache.org/jira/browse/AMQNET-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-475.
--
Resolution: Fixed
Session.DoCreateMessageProducer() does not use the passed in ProducerId
+1
On Tue, Apr 1, 2014 at 7:14 AM, Hadrian Zbarcea hzbar...@gmail.com wrote:
Hi all,
I've cut a release candidate for the 5.9.1 patch release.
I have to update JIRA today to determine the exact number of issues
resolved
and follow up with another email. This patch release is focused on
Jim Gomes created AMQNET-473:
Summary: Add IDisposable interface to IDestination.
Key: AMQNET-473
URL: https://issues.apache.org/jira/browse/AMQNET-473
Project: ActiveMQ .Net
Issue Type
[
https://issues.apache.org/jira/browse/AMQNET-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-333 stopped by Jim Gomes.
Add new provider implementation for ZeroMQ
--
Key: AMQNET-333
[
https://issues.apache.org/jira/browse/AMQNET-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-333.
--
Resolution: Fixed
Fix Version/s: 1.7.0
Add new provider implementation for ZeroMQ
[
https://issues.apache.org/jira/browse/AMQNET-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes closed AMQNET-333.
Add new provider implementation for ZeroMQ
--
Key
[
https://issues.apache.org/jira/browse/AMQNET-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-473.
--
Resolution: Fixed
Updated all providers to support the IDisposable interface on IDestination
objects
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925508#comment-13925508
]
Jim Gomes commented on AMQNET-338:
--
Look at the changes I checked in. It should show
+1
On Mon, Feb 24, 2014 at 6:05 PM, Hiram Chirino hi...@hiramchirino.comwrote:
Hi Everyone,
I've deployed another 1.7 release candidate. This one should fix the
problems with the license file and website issues that were identified
in the first RC.
This release fixes several bugs:
*
+1 for the project roadmap outlined by Dan.
On Mon, Feb 10, 2014 at 10:07 AM, Daniel Kulp dk...@apache.org wrote:
Can I break this down into 3 potential targets?We currently have users
asking about a possible 5.9.1 release to fix some serious issues there. In
addition, we have been
[
https://issues.apache.org/jira/browse/AMQNET-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894019#comment-13894019
]
Jim Gomes commented on AMQNET-470:
--
I vote for Tim's suggested implementation.
Allow
+1 for Google Docs.
On Sat, Feb 1, 2014 at 1:32 PM, artnaseef a...@artnaseef.com wrote:
The list of concerns for the current webconsole, and needs, are documented
on
the following google doc; I hope the use of a google doc is not a concern -
let me know if there's a better place for it.
＋0
I'd prefer leaving it included, but moving to a sub-project seems to be an
acceptable alternative.
On Tue, Jan 28, 2014 at 6:18 AM, Hiram Chirino hi...@hiramchirino.comwrote:
Since there seems to be general agreement that the web-console should
be moved to a sub-project, lets put it to a
[1] -1
[2] 0
[3] +1
[4] +1
Using the webconsole for development/debugging purposes is extremely
helpful. When moving to production systems, it should be a simple matter
to turn it off. This is no different than removing debug code from your
build when deploying.
On Fri, Jan 17, 2014 at 5:33
+1 the ideas that Claus presented below. I like the idea of a simple
drop-in install and a level playing field for replacement consoles. By
having a default headless install, the security of a production
deployment goes way up.
On Mon, Jan 6, 2014 at 12:06 AM, Claus Ibsen claus.ib...@gmail.com
+1
On Thu, Dec 19, 2013 at 2:33 PM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.2
This release focuses on some fixes need in the MSDTC support as well as
some other minor bug fixes found since the 1.6.1 release.
The
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845673#comment-13845673
]
Jim Gomes commented on AMQNET-338:
--
I've just encountered this problem today, and had my
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-338:
-
Fix Version/s: 1.7.0
TcpTransport.cs - Close() taking 30 seconds
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-338:
-
Component/s: Stomp
TcpTransport.cs - Close() taking 30 seconds
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes reassigned AMQNET-338:
Assignee: Jim Gomes
TcpTransport.cs - Close() taking 30 seconds
abort readerThread after a shorter timeout ?
-- 原始邮件 --
*发件人:* Jim Gomes;jgo...@apache.org;
*发送时间:* 2013年12月5日(星期四) 中午11:03
*收件人:* 汤・吉诃德hellkni...@foxmail.com; ActiveMQ Dev
dev@activemq.apache.org;
*主题:* Re: Is it all right to reduce the timeout as a walkaround
The 30 second time-out was meant to give the reader thread a reasonable
time to finish what it is doing and shut itself down gracefully. Once it
times out, then it is forcefully shutdown as a last resort. Normally, the
graceful shutdown should occur very rapidly. If you are just letting the
+1
On Mon, Oct 21, 2013 at 8:44 AM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.Stomp v1.5.4
New in this release:
* Fix for AMQNET-411 FormatException on Non-US Culture based systems.
The binaries and source bundles for the
+1
On Wed, Oct 16, 2013 at 8:04 AM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.1
New in this release:
* Improved Discovery Transport and Agent API
* Improved the multicast discovery agent.
* Added new HTTP based
what introduced the problem.
On Mon, Oct 14, 2013 at 12:57 PM, Jim Gomes e.se...@gmail.com wrote:
All of the 1.6.1 unit tests are failing for me. I run the 1.6.0 unit
tests, and they all succeed. I am running with ActiveMQ 5.9-SNAPSHOT
broker. Perhaps that is the source of the problem. I'll
If I revert the recent changes and build with revision 1488406, then the
unit tests pass. I update to revision 1528606 that includes fixes for
AMQNET-443 and AMQNET-444, then everything breaks.
On Tue, Oct 15, 2013 at 10:24 AM, Jim Gomes e.se...@gmail.com wrote:
I updated to the latest
, even with all of the other changes
included. I think there is something seriously wrong with the OpenWire 10
implementation.
On Tue, Oct 15, 2013 at 10:57 AM, Jim Gomes e.se...@gmail.com wrote:
If I revert the recent changes and build with revision 1488406, then the
unit tests pass. I update
+1
On Mon, Oct 14, 2013 at 4:52 PM, Gary Tully gary.tu...@gmail.com wrote:
Hi all,
I've cut a second release candidate for the 5.9.0 release.
This release has 251 bug fixes and improvements.
It also contains a couple of new features which are summarized here:
, Oct 15, 2013 at 11:12 AM, Jim Gomes e.se...@gmail.com wrote:
I found what introduced the problem. The introduction of OpenWire 10
causes problems. If I change the following line in OpenWireFormat.cs from
PreferredWireFormatInfo.Version = 10;
back
-1
I am still having serious failures with the latest code that was checked
in. I was waiting for it to settle-down before trying to figure out what is
wrong. All of my apps don't work with the latest 1.6.1 code. I switch
back to 1.6.0, and everything works perfectly. The break came with the
Sure. I will try and dig in and find out what is happening.
On Mon, Oct 14, 2013 at 12:27 PM, Timothy Bish tabish...@gmail.com wrote:
On 10/14/2013 03:23 PM, Jim Gomes wrote:
-1
I am still having serious failures with the latest code that was checked
in. I was waiting for it to settle
All of the 1.6.1 unit tests are failing for me. I run the 1.6.0 unit
tests, and they all succeed. I am running with ActiveMQ 5.9-SNAPSHOT
broker. Perhaps that is the source of the problem. I'll update to the
latest 5.9 SNAPSHOT and try again.
On Mon, Oct 14, 2013 at 12:33 PM, Jim Gomes e.se
[
https://issues.apache.org/jira/browse/AMQNET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730094#comment-13730094
]
Jim Gomes commented on AMQNET-440:
--
I would suggest using ITextMessage as the layer
+1
Changing vote to +1, with the provision that the NMS branch porting be
delayed for a short time until supporting infrastructure can be set up to
maintain backward compatibility.
On Tue, Jun 11, 2013 at 5:01 AM, Gary Tully gary.tu...@gmail.com wrote:
+1
On 7 June 2013 15:34, Hiram Chirino
,
If your still feeling hesitant, how about we exclude the NMS bits from
migrating to Git for now? Would that work for you?
On Thu, Jun 13, 2013 at 10:30 AM, Jim Gomes e.se...@gmail.com wrote:
Of particular importance to how we do things, I found the following QA
extremely helpful
-1
We integrate the ActiveMQ NMS build tree into our build process using
external references. Switching to Git will most likely make this
impossible. If there is a solution that can continue to make this seamless
for us, then I could consider changing my vote.
I would also ask what are the
-1
As outlined in my message I sent to the informal discussion. I can repost
on the official voting thread if necessary.
(Sorry for being late.)
On Fri, Jun 7, 2013 at 7:34 AM, Hiram Chirino hi...@hiramchirino.comwrote:
Since there were no objections in the recent to switching from SVN to
in your build process would it?
I find SVN to be too slow for everyday use. Being able to be able to
fully use all the SCM features even when offline is also a very bonus.
On Fri, Jun 7, 2013 at 1:36 PM, Jim Gomes e.se...@gmail.com wrote:
-1
We integrate the ActiveMQ NMS build tree into our
+1
On Mon, Jun 3, 2013 at 8:15 AM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.0
New in this release:
* Adds support for non-blocking redelivery.
* Supports priority backups for Failover transport.
* Supports an
+1
On May 20, 2013 3:00 PM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of the Apache.NMS API v1.6.0.
This package contains the API for the various Apache.NMS clients along
with utility classes and unit test cases against the abstract NMS API.
[
https://issues.apache.org/jira/browse/AMQNET-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643394#comment-13643394
]
Jim Gomes commented on AMQNET-433:
--
Daniel, any additional patch contributions
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes reopened AMQNET-338:
--
Reopening by request for further investigation.
TcpTransport.cs - Close() taking 30
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-338:
-
Affects Version/s: 1.5.6
TcpTransport.cs - Close() taking 30 seconds
[
https://issues.apache.org/jira/browse/AMQNET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-338:
-
Component/s: (was: NMS)
ActiveMQ
TcpTransport.cs - Close() taking 30 seconds
The only drawback is that a lot of the time you can't put your favorite dev
tools on a production machine, and you are stuck with using Notepad to edit
config files.
-1
On Fri, Mar 29, 2013 at 6:06 AM, Christian Posta
christian.po...@gmail.comwrote:
+1
On Thu, Mar 28, 2013 at 10:54 AM,
wrote:
Hi Jim,
Wordpad understands unix line endings so that can be used in those
production situations.
Cheers,
Jon
On Fri, Mar 29, 2013 at 12:34 PM, Jim Gomes e.se...@gmail.com wrote:
The only drawback is that a lot of the time you can't put your favorite
dev
tools on a production
[
https://issues.apache.org/jira/browse/AMQNET-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-423.
--
Resolution: Fixed
Fix Version/s: 1.5.7
This check has been added to the 1.5.x branch
[
https://issues.apache.org/jira/browse/AMQNET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-416:
-
Component/s: ActiveMQ
DTC Ressource ManagerID must be confugurable
[
https://issues.apache.org/jira/browse/AMQNET-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-417:
-
Component/s: ActiveMQ
DTC Recovery should be done once for each application start
[
https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-415.
--
Resolution: Fixed
Client with wrong credentials overloads server when using failover
[
https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-415 stopped by Jim Gomes.
Client with wrong credentials overloads server when using failover
[
https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AMQNET-415 started by Jim Gomes.
Client with wrong credentials overloads server when using failover
Jim Gomes created AMQNET-415:
Summary: Client overloads server with wrong credentials when using
failover
Key: AMQNET-415
URL: https://issues.apache.org/jira/browse/AMQNET-415
Project: ActiveMQ .Net
[
https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-415:
-
Description:
If the ActiveMQ broker has been secured to enforce login credentials, the NMS
client
[
https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-415:
-
Summary: Client with wrong credentials overloads server when using failover
(was: Client overloads
[
https://issues.apache.org/jira/browse/AMQNET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-415:
-
Description:
If the ActiveMQ broker has been secured to enforce login credentials, the NMS
client
+1
On Wed, Feb 20, 2013 at 10:49 AM, Hiram Chirino hi...@hiramchirino.comwrote:
Hi Everyone,
I've deployed a 1.6 release candidate to pickup fixes and new features
since the 1.5 release. It would be nice to release this before Apache Con
NA.
This release features improvements like:
*
Hello All,
I have a procedural question. I know that when source code is tagged, then
no further modifications can be made to that tagged branch. This is to
protect the integrity of the code that was tested and released. However,
is it still permissible to modify the Subversion meta-attributes
Jim Gomes created AMQ-4314:
--
Summary: Client Connections Not Displayed on Admin Webpage
Key: AMQ-4314
URL: https://issues.apache.org/jira/browse/AMQ-4314
Project: ActiveMQ
Issue Type: Bug
Hi Gary,
Got it (AMQ-4315). Thanks for the reply!
-Jim
On Wed, Feb 13, 2013 at 2:04 PM, Gary Tully gary.tu...@gmail.com wrote:
hi jim, that is an error, can you raise a jira issue to track. thanks!
On 13 February 2013 18:58, Jim Gomes e.se...@gmail.com wrote:
Hello All,
I noticed
[
https://issues.apache.org/jira/browse/AMQ-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577981#comment-13577981
]
Jim Gomes commented on AMQ-4314:
This was introduced in 5.8.0. I just re-checked 5.7.0
Excellent. Thanks, Christian!
On Wed, Feb 13, 2013 at 4:06 PM, Christian Posta
christian.po...@gmail.comwrote:
Fixed!
On Wed, Feb 13, 2013 at 3:14 PM, Jim Gomes e.se...@gmail.com wrote:
Hi Gary,
Got it (AMQ-4315). Thanks for the reply!
-Jim
On Wed, Feb 13, 2013 at 2:04
+1
On Wed, Feb 6, 2013 at 11:55 AM, Gary Tully gary.tu...@gmail.com wrote:
Hi all,
I've just cut a release candidate for the 5.8.0 release. This release has
160 bug fixes and improvements.
It also contains a couple of new features which are summarized here:
+1
On Thu, Nov 8, 2012 at 6:13 AM, Gary Tully gary.tu...@gmail.com wrote:
I agree, it has not had much love over the past few releases and the
implementation over a single channel will never scale, + there is the
recovery problem.
The theory is great though, no infrastructure required. We
+1
On Mon, Nov 5, 2012 at 3:00 PM, Hiram Chirino hi...@hiramchirino.comwrote:
Hi Everyone,
I've deployed a 1.5 release candidate to pickup fixes and new features
since the 1.4 release. This release features improvements like:
[APLO-30] - Support the Openwire Protocol
[APLO-262] -
Hi Jasper,
It is integrated with Subversion via AnkhSVN. Do you have AnkhSVN
installed? Have you applied any Service Packs to Visual Studio? Just
trying to figure out what you have configured.
You can download AnkhSVN from here: http://ankhsvn.open.collab.net/downloads
I usually go with the
+0
I'm neutral on this one. No strong feelings either way, unless there was a
show-stopper bug fixed in the core product (not counting the XSS problem in
the demos).
On Mon, Oct 22, 2012 at 9:15 AM, Gaurav Sharma
gaurav.cs.sha...@gmail.comwrote:
+1
We might also consider rolling any patches
+1
On Tue, Oct 2, 2012 at 9:40 AM, Dejan Bosanac de...@nighttale.net wrote:
Hi all,
I've just cut second release candidate for the 5.7.0 release. This is
mostly maintenance release with nearly 200 bug fixes and improvements.
It also contains a couple of new features which are summarized
Jim Gomes created AMQ-4090:
--
Summary: Missing svn:ignores
Key: AMQ-4090
URL: https://issues.apache.org/jira/browse/AMQ-4090
Project: ActiveMQ
Issue Type: Bug
Components: Broker
[
https://issues.apache.org/jira/browse/AMQ-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQ-4090:
---
Description:
There are missing *svn:ignore* attributes for some new files and folders that
are created during
Any chance of getting
AMQ-4090https://issues.apache.org/jira/browse/AMQ-4090fixed for the
release? It shouldn't affect the artifacts, since it is a
repository only change.
On Tue, Oct 2, 2012 at 10:50 AM, Jim Gomes e.se...@gmail.com wrote:
+1
On Tue, Oct 2, 2012 at 9:40 AM, Dejan Bosanac de
+1
On Mon, Oct 1, 2012 at 6:52 AM, Dejan Bosanac de...@nighttale.net wrote:
Hi all,
I've just cut a release candidate for the 5.7.0 release. This is
mostly maintenance release with nearly 200 bug fixes and improvements.
It also contains a couple of new features which are summarized here:
Jim Gomes created AMQ-4084:
--
Summary: Linux/Unix Files Have Incorrect EOL When Packaged
Key: AMQ-4084
URL: https://issues.apache.org/jira/browse/AMQ-4084
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQ-4084:
---
Attachment: windows-bin.xml.patch
Set the EOL for Unix specific files.
Linux/Unix Files Have
Hello All,
In the ActiveMQ repository, we have a few platform specific script files
for launching ActiveMQ on (Li|U)nix platforms. Specifically, the
*activemq* and
*activemq-admin* script files. Currently, most, but not all, of these
files have been flagged in Subversion to have the'*eol-style:
still edit the source files in the
format most natural on the dev platform, but still get the correct EOL
conversion in the final distribution target.
On Tue, Sep 25, 2012 at 11:58 AM, Jim Gomes e.se...@gmail.com wrote:
Hello All,
In the ActiveMQ repository, we have a few platform specific
25, 2012 at 2:25 PM, Jim Gomes e.se...@gmail.com wrote:
+1. I like that solution.
On Tue, Sep 25, 2012 at 1:35 PM, Hiram Chirino hi...@hiramchirino.comwrote:
The maven assembly plugin's descriptor should support specifying which EOL
style to use when it adds the file to the distribution
+1
On Mon, Sep 10, 2012 at 8:21 AM, Gaurav Sharma
gaurav.cs.sha...@gmail.comwrote:
+1
On Sep 10, 2012, at 6:12, Timothy Bish tabish...@gmail.com wrote:
+1
On Mon, Sep 10, 2012 at 8:34 AM, Hiram Chirino hi...@hiramchirino.com
wrote:
+1
On Mon, Sep 10, 2012 at 5:40 AM, Claus
+1
On Mon, Aug 27, 2012 at 1:05 PM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.Stomp v1.5.3.
New in this release:
* This release focuses on stability fixes for issues found since the
v1.5.2 release. The release should work much
[
https://issues.apache.org/jira/browse/AMQNET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-395.
--
Resolution: Fixed
ResponseCorrelator transport is not stopped when Connection is closed
[
https://issues.apache.org/jira/browse/AMQNET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-394.
--
Resolution: Fixed
Zombie Consumer is created after failover
101 - 200 of 905 matches
Mail list logo
