Sinan doesn't actually care where the app files are. It does that for
a couple of reasons. The biggest is that there isn't actually a
standard for project layout. There is a convention, using lib, but
thats not really a standard.
The other reason is so that single app projects can ignore the usual
project structure. Sinan will happily build a project that looks like
ktuo
|- ebin
|- src
as easily as a project that looks like
sinan
|- lib
|-someapp1
|-someapp2
So I am more then happy the under directory of sinan from server to
lib. I am much less confident of imposing a directory structure on
projects.
On Thu, Feb 18, 2010 at 12:57 PM, Martin Logan <[email protected]> wrote:
> The best would be to move both of those subdirs under the base lib
> directory. That would bring the sinan app into compliance with the
> standard. Sinan itself shoudl also look for a lib directory and
> enforce its presence I think.
>
> On Wed, Feb 17, 2010 at 5:08 PM, Tristan Sloughter
> <[email protected]> wrote:
>> Sinan itself does not have a lib directory. Would it be a good idea to turn
>> server into lib and maybe move client to support? Or priv? Or something.
>> What is the standard?
>> Tristan
>>
>> --
>> 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.
>>
>
> --
> 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.
>
>
--
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.
