--- On Wed, 9/16/09, Adam Murdoch <[email protected]> wrote: > From: Adam Murdoch <[email protected]> > Subject: Re: [gradle-dev] GUI > To: [email protected] > Date: Wednesday, September 16, 2009, 9:02 PM > > > Hans Dockter wrote: > > > > On Sep 16, 2009, at 10:31 PM, Mike wrote: > > > >> > >> --- On Wed, 9/16/09, Tomek Kaczanowski <[email protected]> > wrote: > >> > >>> From: Tomek Kaczanowski <[email protected]> > >>> Subject: Re: [gradle-dev] GUI > >>> To: [email protected] > >>> Date: Wednesday, September 16, 2009, 8:02 PM > >>> Hi Steve, > >>> > >>> I am sorry to report, that my first try on GUI > was rather > >>> unsuccessful. :( > >> > >> That's unfortunate. The first issue as you guessed > has to do with file permissions. The shell script isn't > marked as executable when gradlew expands gradle into your > home directory. Its marked as executable in the zip file it > downloads, but the unzip process is not preserving it. > > > > Could you file a Jira with fix for 0.8 for that? We > need to add some logic to the wrapper to fix this. > > > > A better solution would be for the UI to not use the > scripts. > > > Adam
I agree. We originally tried to go down the path of executing things directly with gradle, but there are several things the gradle-launching scripts are setting up for us and we didn't want to duplicate that information in code and in 2 scripts (for each OS). If this information could be pulled outside of the scripts so that it could be launched via a single java command (which would be the only thing the scripts would do) that would be great. But that might not be practical. There's alot going on in there. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > Mike Automated Logic Research Team --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
