Ok, it's good that there is way to change the name of the root project in
some way. But as you mentioned it is over the top that it requires a
separate file.
Perhaps we should incorporate the settings.gradle file into the build.gradle
file as a settings { ... } block that needs to be the first thing in the
build.gradle file ?
Jira: http://jira.codehaus.org/browse/GRADLE-335
2008/12/27 Hans Dockter <[email protected]>
> Hi Tom,
>
>
> On Dec 27, 2008, at 12:10 AM, 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.
>>
>> Any thoughts/ ideas on this would be appreciated.
>>
>
> This is an interesting point. It is an issue only for the naming of the
> root project. Some background regarding the naming of a project. In a
> multi-project build, you can access another project from a build script of a
> subproject (e.g. project(':somepath')). Therefore the projects need names
> before the build scripts are evaluated (an exception would be the root
> project, which can be accessed with project(':')). What you can do already,
> is to assign a non default project name in the settings.gradle file. I'm not
> sure what the best solution would be for the Hudson scenario. Just wanted to
> point out some background information. One solution would be to use the
> settings.gradle to assign a defined name to the root project. This is an
> ugly solution for single project builds, as you usually would not have a
> settings.gradle file. This brings us back again to our discussion at Devoxx,
> about getting rid of the settings.gradle altogether.
>
> Could you file a Jira?
>
> - Hans
>
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
