2009/1/5 Hans Dockter <[email protected]> > > On Dec 28, 2008, at 10:44 AM, Hans Dockter wrote: > > >> On Dec 28, 2008, at 10:31 AM, Adam Murdoch wrote: >> >> >>> >>> Tom Eyckmans wrote: >>> >>>> I tried the Gradle Hudson plugin and stumbled upon an issue. >>>> >>>> Hudson jobs are run from a <job-name>/workspace directory. Because of >>>> this the Gradle way of working (depending on the directory name for the >>>> project name) is broken; the archives that are created by libs/ dists won't >>>> get the correct name (if you don't set the archiveBaseName). >>>> >>>> As I mentioned earlier, the solution is simple set the archiveBaseName >>>> if you can't rely on the directory name, but perhaps we want to make sure >>>> builds are repeatable/ consistent without knowledge of the directory that >>>> is >>>> used. >>>> >>>> >>> I think so. >>> >>> One possibility is to use the name of the build file to determine the >>> default project name, and encourage people to call their build files >>> something other than 'build.gradle'. It would be kind of a shame if every >>> build file in the world was called 'build.gradle' and we lost that source of >>> information. Plus it's a pain to find a particular build file in the IDE >>> when there's dozens of them and they all have the same name. >>> >> >> Wow, that's an interesting idea and so simple. One negative aspect might >> be that it is harder to figure out what is the build script. But if we get >> rid of the settings.gradle file, it will be simply the file with the .gradle >> extension. >> > > I have filed a Jira: http://jira.codehaus.org/browse/GRADLE-348 > > I already created http://jira.codehaus.org/browse/GRADLE-335 for this. Should we link them or close one?
> > - Hans > > -- > Hans Dockter > Gradle Project lead > http://www.gradle.org > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
