Yep, I understand *how* to do it. Again, I am asking if there is a reason to
not do it there. Seems like it would be the ideal place to write it by
default so just leery there is a reason that is not the case already.
Like thinking about it some more, this directory is usually version controlled
which would make it tough to manage in terms of the downoaded gradle
distributions and making sure they do not become versioned.
On Thursday, February 10, 2011, at 11:26 am, Jim Moore wrote:
> task wrapper(type: Wrapper, description: 'Create a wrapper script for
> Gradle') {
>
> gradleVersion = '0.9.2'
>
> jarFile = '.gradle-wrapper/gradle-wrapper.jar'
>
> }
>
> On Thu, Feb 10, 2011 at 11:27 AM, Steve Ebersole <[email protected]>wrote:
> > I am trying to figure out the reason to not have Wrapper generate the jar
> > and
> > properties into .gradle/ as opposed to gradle/. Which got me to
> > wondering what the original reason for that desicion was. Is there a
> > downside/issue to
> > using .gradle/ for these?
> >
> > ---
> > Steve Ebersole <[email protected]>
> > http://hibernate.org
> >
> > ---------------------------------------------------------------------
> >
> > To unsubscribe from this list, please visit:
> > http://xircles.codehaus.org/manage_email
---
Steve Ebersole <[email protected]>
http://hibernate.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
