Hi Jim,
Actually, I was working on the dependency problem last yesterday /
last night. I went with the solution that has been working for us
very well in the Java space. And that's using a maven style remote
repository to store deployed artifacts.
I've updated the nant builds so that they auto
Just remembered.. I need to check to see if I can update the VS
project files to refer to dependencies from the local repo...
Otherwise I think I'm gonna have to copy them into the $project/lib
folder as part of the build process.
On 11/1/07, Hiram Chirino [EMAIL PROTECTED] wrote:
Hi Jim,
Yay.. your able to use environment variables in the VS project files.
I've now updated them to also refer to the nant repo to look for
dependencies.
On 11/1/07, Hiram Chirino [EMAIL PROTECTED] wrote:
Just remembered.. I need to check to see if I can update the VS
project files to refer to
[
https://issues.apache.org/activemq/browse/AMQ-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40541
]
Lari Hotari commented on AMQ-1169:
--
My problem went away after using backport-util-concurrent 2.1 on client (and
PooledConnection.close() doesn't always close the ActiveMQConnection
Key: AMQ-1484
URL: https://issues.apache.org/activemq/browse/AMQ-1484
Project: ActiveMQ
Issue Type:
Reorganize the modules into independent projects
Key: AMQNET-72
URL: https://issues.apache.org/activemq/browse/AMQNET-72
Project: ActiveMQ .Net
Issue Type: Improvement
Components:
Error in source include name
Key: AMQNET-73
URL: https://issues.apache.org/activemq/browse/AMQNET-73
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ Client
Affects Versions: 1.0
[
https://issues.apache.org/activemq/browse/AMQNET-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-73:
Attachment: AMQNET-73.patch
Error in source include name
[
https://issues.apache.org/activemq/browse/AMQNET-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-72:
Attachment: (was: Apache.NMS.ActiveMQ-VendorSolution.patch)
Reorganize the modules into
And yes nant was a sort of requirement before.. It's the only build
system that works across frameworks and we do want to support mono
too. It also will detect and compile against all available frameworks
on your machine. So we will use it at least when we are doing release
builds.
On 11/1/07,
[
https://issues.apache.org/activemq/browse/AMQNET-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-72:
Attachment: Apache.NMS.MSMQ-VendorSolution.patch
Apache.NMS.EMS-VendorSolution.patch
[
https://issues.apache.org/activemq/browse/AMQNET-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes updated AMQNET-74:
Attachment: AMQNET-74.patch
ActiveMQ provider unable to load OpenWire marshaller
Ok.. I got it setup for the NMS.ActiveMQ module. Easy enough.
Please let me know if that's what you were requesting.. I'll
replicated that to the other modules if it's what you were looking
for.
On 11/1/07, Hiram Chirino [EMAIL PROTECTED] wrote:
Ok.. I'll try out setting up the extenal vendor
[
https://issues.apache.org/activemq/browse/AMQ-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies updated AMQ-1485:
Component/s: Broker
Enable setting properties for sizing indexes used by the default reference
store
Enable setting properties for sizing indexes used by the default reference
store for AMQStore
-
Key: AMQ-1485
URL: https://issues.apache.org/activemq/browse/AMQ-1485
Yes, that is what I was going for. I originally had not placed the
Apache.NMS in a vendor sub-directory, but I'm OK with that. I really like
the external repository reference when doing a checkout.
The other projects are easy to change as well, except for MSMQ. It still
had a dependency on the
Sorry, I meant the patch I posted to [AMQNET-72]. Reference the
Apache.NMS.MSMQ-VendorSolution.patch file.
On 11/1/07, Jim Gomes [EMAIL PROTECTED] wrote:
Yes, that is what I was going for. I originally had not placed the
Apache.NMS in a vendor sub-directory, but I'm OK with that. I really
Allow message logs for AMQStore to ve archived instead of deleted when they are
discarded
-
Key: AMQ-1486
URL: https://issues.apache.org/activemq/browse/AMQ-1486
There's a potential fix for this I've just added to trunk - would it
be possible to build the latest and test ?
cheers,
Rob
http://rajdavies.blogspot.com/
On Nov 1, 2007, at 9:47 PM, Andrew Miller wrote:
We've been using ActiveMQ in an infrastructure refresh project, and
have run
Hi Hiram,
It looks like we are missing the vs2005-stomp-tests.csproj in the new
organization. This should be included as part of the
Apache.NMS.ActiveMQproject and added to the
vs2005-activemq.sln file.
Thanks,
Jim
On 11/1/07, Hiram Chirino [EMAIL PROTECTED] wrote:
Ok.. I got it setup for
Thanks for the fix! We're running the test now... Parameters:
SVN version: 591163
Client jar: Updated to 5.0-20071028.173739
We haven't seen any of the original IndexOutOfBounds exception messages,
even after about 1.2 million Enqueues. However, the consumers appear to be
stuck and unable
21 matches
Mail list logo
