Hi Hans,
Hans Dockter wrote:
On Nov 27, 2008, at 1:10 AM, Jason Sankey wrote:
I'm new to gradle, so forgive me if my ignorance is showing. I've
just been playing around with my first gradle builds, and noticed some
behaviour that seems counter-intuitive. I'm not sure if it is
misunderstanding on my part or not.
My case is this: I have a project that I do not want to name after the
containing directory. Easy enough, I just set the project name in my
build.gradle file:
name = 'foo'
I expected this to also change the name of the jar file produced by
libs, backed up by the documentation which indicates archivesBaseName
defaults to the project name. Unfortunately, though, the jar
continues to get named after the directory. If I'm reading the gradle
code correctly, it appears that archivesBaseName is set to the project
name when the project is created. This I guess means that my change
to the project name comes too late to affect the archives. Would it
make sense to leave archivesBaseName as null and return the current
value of name in that case instead? Or am I missing something?
You are right. This is a bug. I have filed a Jira:
http://jira.codehaus.org/browse/GRADLE-315
Thanks for the quick response!
Cheers,
Jason
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
