Skip to content
This repository has been archived by the owner on Nov 17, 2020. It is now read-only.

rabbitmq-common dep conflict with qdate ? #139

Closed
jhw opened this issue Oct 17, 2016 · 4 comments
Closed

rabbitmq-common dep conflict with qdate ? #139

jhw opened this issue Oct 17, 2016 · 4 comments

Comments

@jhw
Copy link

jhw commented Oct 17, 2016

Hi,

I have an erlang.mk project which has been using amqp_client and qdate happily for a long time. On a recent 'make distclean' I am suddenly getting the following -

===> Errors generating release
Duplicated modules:
ec_semver_parser specified in erlware_commons and rabbit_common
ec_semver specified in erlware_commons and rabbit_common

qdate pulls in erlware_commons and amqp_client pulls in rabbit_common.

@essen suggests this is a bona fide naming conflict; it looks to me the issue may have been introduced on the rabbitmq-common side.

Is this something that could/should be fixed ?

Thank you -

@choptastic
Copy link

choptastic commented Oct 18, 2016

This is indeed a naming conflict. As rabbitmq-common recently copied ec_semver_* files from erlware_commons rather than adding it as a dependency.

One suggestion would be to rename the copied modules to avoid the naming conflict - something like rabbit_semver and rabbit_semver_parser are (to me) the obvious choices. Otherwise any project using rabbit and erlware_commons will generate these naming conflicts.

That, or just use erlware_commons as a dependency (though I understand apprehension to adding more dependencies for one or two modules).

Edit: Updated the link to the commit that brought in ec_semver_*

@michaelklishin
Copy link
Member

Renaming a module sounds like an easy way out to me.

@essen
Copy link
Collaborator

essen commented Nov 24, 2016

Also exists with mochinum and mochiweb_util. I will send a PR now.

@essen
Copy link
Collaborator

essen commented Nov 24, 2016

Should be good to review and merge.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants