To be precise, Tellurium actually loads the configuration file TelluriumConfig.groovy first from the project root. If not found, it loads it from the class path. You can still keep the configuration file at the project root.
Thanks, Jian On Thu, Apr 1, 2010 at 9:01 AM, Jian Fang <[email protected]> wrote: > I see, you prefer the existing name TelluriumConfig.groovy, right? > > Tellurium needs to load configuration file first and it is not a good idea > to add another configuration > file. The other option would be to give Tellurium to select one of couple > files to load. > > TelluriumConfig.groovy gets compiled by gmaven itself would not do any harm > and just does not > look cool. If people prefer the existing name, we can keep it. > > Thanks, > > Jian > > On Thu, Apr 1, 2010 at 4:29 AM, Robert Fletcher < > [email protected]> wrote: > >> I'm working on integrating Tellurium with Grails and the existing name >> would be more in line with conventions there. Would it be possible to >> tell Tellurium which file to use? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "tellurium-users" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<tellurium-users%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/tellurium-users?hl=en. >> >> > -- You received this message because you are subscribed to the Google Groups "tellurium-users" 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/tellurium-users?hl=en.
