Please response by April 5th. If no objections, I will go ahead to rename it.
Thanks, Jian On Thu, Apr 1, 2010 at 12:40 AM, Jian Fang <[email protected]> wrote: > Hi All, > > I like to rename Tellurium configuration file from TelluriumConfig.groovy > to tellurium.conf. > > The reason is that TelluriumConfig.groovy could be compiled by Gmaven after > we move > it to src/test/resources directory. We could use GMaven configuration as > follows to exclude > the compilation, > > <plugin> > <groupId>org.codehaus.gmaven</groupId> > <artifactId>gmaven-plugin</artifactId> > <configuration> > <providerSelection>1.7</providerSelection> > <targetBytecode>${java-version}</targetBytecode> > </configuration> > <executions> > <execution> > <goals> > <goal>generateStubs</goal> > <goal>compile</goal> > <goal>generateTestStubs</goal> > <goal>testCompile</goal> > </goals> > <configuration> > <sources> > <fileset> > > <directory>${pom.basedir}/src/main/groovy</directory> > <includes> > > <include>**/*.groovy</include> > </includes> > </fileset> > <fileset> > > <directory>${pom.basedir}/src/test/groovy</directory> > <includes> > <include>**/*.groovy</include> > </includes> > </fileset> > <fileset> > > <directory>${pom.basedir}/src/test/resources</directory> > <excludes> > <exclude>**/*.groovy</exclude> > </excludes> > </fileset> > </sources> > </configuration> > </execution> > </executions> > </plugin> > > But this is really awkward. If we change the name to tellurium.conf, we > don't need any > extra work. > > Another reason is that tellurium.conf is short and it is consistent with > name conversions in > other frameworks. > > Any objections? > > Thanks, > > Jian > -- 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.
