[rabbitmq-discuss] lager vs sasl error log

Fri Mar 29 08:12:50 GMT 2013

Tim,
Don't worry about this issue. I have probably misused the VERSION number.

The problem is we have custom plug-ins (another product) on top of RabbitMQ, which means the RabbitMQ VERSION is different from our plug-in VERSION.
Then, if RabbitMQ is 3.0.2 and our plug-in is 0.0.4 the lager will be compiled twice: as lager-2.0.0-rmq3.0.2 and then as lager-2.0.0-rmq3.0.2. The rabbitmq_lager/dist directory will however store only one .ez file-- the one that will be compiled later. This creates a problem for packaging, because the name of the .ez file in rabbitmq_lager/dist depends on the build sequence, which is not very nice.

Lesson learned: The VERSION number shall indicate the RabbitMQ version for all plug-ins.

Petr

-----Original Message-----
From: rabbitmq-discuss-bounces at lists.rabbitmq.com [mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Tim Watson
Sent: 28. března 2013 14:44
To: Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] lager vs sasl error log

On 28 Mar 2013, at 13:18, Gotthard, Petr wrote:

> Thanks Tim,
> 
> It compiles, runs and works, but--- there's a trouble (at least here) with the "rmq" suffix (the name is something like lager-2.0.0-rmq0.0.0-git9719370.ez)
> 
> The RMQ numbers seem to be taken from the VERSION parameter. Which means that if multiple plug-ins have different version, different version of the lager is created for each of the plugins (rmq0.0.0, rmq0.0.1, rmq0.0.4) and these versions overwrite each other, which creates a mess.
> 

I'm not really sure why this would happen?

> Can various plug-ins can have different version, but still be compiled against the same rabbit?
> 

I don't think so - when you build from source, all the plugins (and the broker) should pick up the same VERSION as each other. If you're not building from source, I'm not sure which constraint you're running into. What are the symptoms (i.e., what goes wrong)?