+1
Tested:
pyngus unit tests (python 2.7 and 3.4)
oslo.messaging unit and functional tests for AMQP 1.0 driver
rsyslog output module
- Original Message -
> From: "Justin Ross"
> To: users@qpid.apache.org
> Sent: Friday, July 1, 2016 10:20:01 PM
> Subject: [VOTE] Release Qpid Proton 0
No I don't think so.
Steve Huston
(sent from my iPhone - please excuse brevity and typos)
> On Jul 6, 2016, at 3:32 PM, loremIpsum1771 wrote:
>
> I'm not sure. I just tried deleting the cache from the CMake GUI and I then
> re-ran: cmake -G "Visual Studio 12 2013"
> C:\Users\I664761\Downloads
I'm not sure. I just tried deleting the cache from the CMake GUI and I then
re-ran: cmake -G "Visual Studio 12 2013"
C:\Users\I664761\Downloads\qpid-cpp-0.34 but the filepath seems to still be
the same. I have both Cmake and Boost in my downloads folder and I can't
move them to program files becau
Not Boost... the cmake cache in your qpid build stores that stuff. You can
either run the cmake gui and delete those variables, or delete the whole cache
file.
> -Original Message-
> From: loremIpsum1771 [mailto:celij...@gmail.com]
> Sent: Wednesday, July 06, 2016 2:53 PM
> To: users@qpi
Ok I tried deleting the environment variable for BOOST_ROOT and creating it
again as it is currently set to C://Downloads/boost_1_61_0 but for
some reason, whenever I run CMake, I still get the same error with the same
file path showing up so I'm not really sure what's going on. I also tried
runnin
The CMake find module for Boost is rather finicky. The BOOST_ROOT env variable
should be set to the 'root', which is the directory above the one where your
boost library binaries are. If that doesn't work, try setting BOOST_LIBRARYDIR
explicitly - that is more direct.
-Steve
> -Original Me
Oh ok, it seems that those missing packages are in fact not causing a
problem. For some reason though, it seems that CMake is able to find only
some of the Boost libraries, but not others:
https://gist.github.com/loremIpsum1771/fc1d912bbe5a741325cdd259f7a53837
I created the BOOST_ROOT environment
On 6 July 2016 at 17:13, Andrew Stitcher wrote:
>
>> NOTE: gpg gave me this:
>>
>> gpg --verify qpid-proton-0.13.1.tar.gz.asc qpid-proton-0.13.1.tar.gz
>> gpg: Signature made Fri 01 Jul 2016 10:08:26 PM EDT using RSA key ID
>> C6B459DB
>> gpg: Good signature from "Justin Ross (CODE SIGNING KEY) >
On 6 July 2016 at 17:57, Gordon Sim wrote:
> On 06/07/16 17:42, Gordon Sim wrote:
>>
>> On 06/07/16 17:14, Dale Green wrote:
>>>
>>> I have an update on this issue.
>>>
>>> According to Microsoft, state=Released is supported and now I can confirm
>>> that this is true. If the message is released d
On 6 July 2016 at 17:50, Robbie Gemmell wrote:
> Hi Dale,
>
> It isnt invalid from a protocol perspective, as dispositions only
> actually refer to session-scoped information, not link
> (consumer/producer) scoped information. I deleted an overly
> complicated description of why that is. ServiceB
On 06/07/16 17:57, Gordon Sim wrote:
On 06/07/16 17:42, Gordon Sim wrote:
On 06/07/16 17:14, Dale Green wrote:
I have an update on this issue.
According to Microsoft, state=Released is supported and now I can
confirm
that this is true. If the message is released during the lifetime of the
cons
On 06/07/16 17:42, Gordon Sim wrote:
On 06/07/16 17:14, Dale Green wrote:
I have an update on this issue.
According to Microsoft, state=Released is supported and now I can confirm
that this is true. If the message is released during the lifetime of the
consumer (before Detach), the same message
Hi Dale,
It isnt invalid from a protocol perspective, as dispositions only
actually refer to session-scoped information, not link
(consumer/producer) scoped information. I deleted an overly
complicated description of why that is. ServiceBus isnt
necessarily wrong in ignoring the dispositions give
On 06/07/16 17:14, Dale Green wrote:
I have an update on this issue.
According to Microsoft, state=Released is supported and now I can confirm
that this is true. If the message is released during the lifetime of the
consumer (before Detach), the same message is immediately unlocked and is
availa
I have an update on this issue.
According to Microsoft, state=Released is supported and now I can confirm
that this is true. If the message is released during the lifetime of the
consumer (before Detach), the same message is immediately unlocked and is
available for the same consumer or others dep
> NOTE: gpg gave me this:
>
> gpg --verify qpid-proton-0.13.1.tar.gz.asc qpid-proton-0.13.1.tar.gz
> gpg: Signature made Fri 01 Jul 2016 10:08:26 PM EDT using RSA key ID
> C6B459DB
> gpg: Good signature from "Justin Ross (CODE SIGNING KEY) e.org>"
> gpg: WARNING: This key is not certified with
On Tue, 2016-07-05 at 13:33 -0700, loremIpsum1771 wrote:
> Yes, "" is just being used as a placeholder. I created a new
> builds/qpid directory on the C drive and then ran the command: cmake
> -G
> "Visual Studio 12 2013" C:\Users\I664761\Downloads\qpid-cpp-0.34
> after doing
> which I got the foll
Hi.
I've posted a successful build log for reference:
http://people.apache.org/~chug/qpid-build-log-vs2012-x86.txt
I don't have Boost for VS2013 so can't build with that version.
This example using VS2012 is pretty representative of any build I've seen.
Ruby has a confusing log message from a b
+1
I tested the staged Maven artefacts using the Joram Testsuite with
Qpid JMS Client 0.10.0 and Java Broker 6.0.4.
No issues encountered.
On 6 July 2016 at 07:40, Jakub Scholz wrote:
> +1
>
> I checked Proton C++ bindings as well as trunk versions of Qpid C++ broker
> and Qpid Messaging client
19 matches
Mail list logo
