<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"></blockquote><font color="#0f61c8"><br></font>It seems I've run into the problem again, with both RabbitMQ and CloudI both using pqueue. This seems like a problem that should plague a lot of people. Isn't there a preferred way of dealing with this?<br><font color="#0f61c8"><br></font>Thanks,<br>Lee<br><font color="#0f61c8"><br><br><br></font>On 7 May 2013, at 19:49, Alex Shneyderman <<a href="mailto:a.shneyderman@gmail.com">a.shneyderman@gmail.com</a>> wrote:<br><font color="#0f61c8"><br><br></font><blockquote type="cite"><div><blockquote type="cite"></blockquote>the safest thing to do is to use jsx for json in your own<br><blockquote type="cite"></blockquote>applications. Obviously you will be back to square one if two of your<br><blockquote type="cite"></blockquote>deps will depend on mochijson2 but you did not state that this is your<br><blockquote type="cite"></blockquote>current problem, so switching to jsx (which is actually a lot more<br><blockquote type="cite"></blockquote>enjoyable interface-wise) will take you a long way.<br><blockquote type="cite"></blockquote><font color="#007316"><br></font><blockquote type="cite"></blockquote>another solution is to rename mochijson2 to say something<br><blockquote type="cite"></blockquote>leesylvester_mochijson2 in your application.<br><blockquote type="cite"></blockquote><font color="#007316"><br></font><blockquote type="cite"></blockquote>cheers.<br><blockquote type="cite"></blockquote><font color="#007316"><br></font><blockquote type="cite"></blockquote>On Tue, May 7, 2013 at 2:41 PM, Lee Sylvester <<a href="mailto:lee.sylvester@gmail.com">lee.sylvester@gmail.com</a>> wrote:<br><blockquote type="cite"><blockquote type="cite"></blockquote>Hi guys,<br><blockquote type="cite"></blockquote><font color="#680900"><br></font><blockquote type="cite"></blockquote>So, I'm compiling CloudI into my app (safest option), but I'm getting a conflict when I compile. The app I have using Mochijson2, but so does ecouchdb which is part of CloudI. Thus, when I compile my app (well, actually, it's when I generate a release), I now get the error "{'EXIT',{{badmatch,{error,"Module mochijson2 potentially included by two different applications: ecouchdb and mochijson2."}},". I've removed the mochijson2.erl file in the ecouchdb app, hoping that would force the compiler to make ecouchdb use the app version of Mochijson2, but that did nothing. Is there something I can add to my reltool.config to fix this? I've Googled, but nothing that made sense came up.<br><blockquote type="cite"></blockquote><font color="#680900"><br></font><blockquote type="cite"></blockquote>Thanks,<br><blockquote type="cite"></blockquote>Lee<br><blockquote type="cite"></blockquote><font color="#680900"><br></font><blockquote type="cite"></blockquote><font color="#680900"><br></font><blockquote type="cite"></blockquote>_______________________________________________<br><blockquote type="cite"></blockquote>erlang-questions mailing list<br><blockquote type="cite"></blockquote><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote></div></blockquote></div><br></body></html>