That is going to create problems on a number of levels. The first is that subdirectories in erlang have semantic meaning. That is, if its a subdirectory it should be a package if its not that is unexpected. Also more and more the tools are expecting sub directories to be packages. We have had problems with this in the company I work for. It could very well be that this problem is related to that. I really suggest that you either flatten your directory structure or convert them to packages.
I have the feeling that packages are going to be first class citizens before too much longer in any case. Eric On Mon, Mar 21, 2011 at 10:52 AM, Martin Logan <[email protected]> wrote: > It is just a subdir of src. No packages. It is a very convenient > organizer for me though to separate out commands from policy neutral > driver layer stuff. > > On Mon, Mar 21, 2011 at 9:09 AM, Eric Merritt <[email protected]> wrote: >> Do you have this in your erlp repo somewhere? >> >> are you using packages or just modules in a subdirectory of source? >> >> On Mon, Mar 21, 2011 at 12:35 AM, Martin Logan <[email protected]> >> wrote: >>> Eric, I have some files in >>> >>> src/commands >>> >>> within an application. Sinan can't find them to output coverage info. >>> Not sure if this is a sinan thing or a coverage tool thing. >>> >>> -- >>> Martin Logan >>> Erlang & OTP in Action (Manning) http://manning.com/logan >>> http://twitter.com/martinjlogan >>> http://erlware.org >>> >> > > > > -- > Martin Logan > Erlang & OTP in Action (Manning) http://manning.com/logan > http://twitter.com/martinjlogan > http://erlware.org > -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
