that is a good point - version is an interesting one. Name is easy - name of the containing directory by default. Version - hmm, yeah, version of the application if the project is only a single app. If the project has a lib dir and only one app, then the version of the app that it contains, if the project has many but one of the apps has the same name as the containing dir then use that version. Faxien has this pattern and I suspect many other projects as well. If none of these conditions occur the user could supply the version at the commandline or use a sinan.cfg.
Cheers, Martin On Mon, Nov 1, 2010 at 9:14 AM, Eric Merritt <[email protected]> wrote: > Well, I lean that way as well. and that works for finding the project root > in projects that are layed out in a normal way. However, there is > information that the sinan.cfg provides that doesn't exist anywhere else > (project version, description, etc). Also it doesn't work in projects that > are not layed out in the normal way. > > Of course, we could try to come up with some reasonable defaults and 'do > the right thing' in those projects that are layed normally and require it in > projects that are layed out more differently. > El oct 31, 2010, a las 9:54 p.m., Martin Logan escribió: > > It does not work but I agree that it should. It should see either an ebin > dir directory or a lib dir with apps beneith it and do the right thing. If > those conditions don't exist and there is no sinan.cfg then it should return > an error. > > On Sun, Oct 31, 2010 at 4:55 PM, Tristan Sloughter < > [email protected]> wrote: > >> Eric, I thought sinan was able to compile even if a sinan.cfg file did not >> exist? I can not do this with the newest sinan. >> >> 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]<erlware-dev%[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]<erlware-dev%[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.
