performance

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

performance

Ittay Dror
Hi,

I've noticed that Gradle is much slower compared to ant. A build that copies only one file takes ~6 seconds.

Are there any thoughts of focusing on the aspect of performance? What about gradle compiling the gradlefile into a .class file and using it in subsequent builds (if not changed of course)?

Thank you,
Ittay
Reply | Threaded
Open this post in threaded view
|

Re: performance

hans_d
Administrator

On May 28, 2008, at 5:19 AM, Ittay Dror wrote:

>
> Hi,
>
> I've noticed that Gradle is much slower compared to ant. A build  
> that copies
> only one file takes ~6 seconds.

Gradle is slower than Ant, but six seconds is a lot.

On my machine (Mac OS X and 1.5 year old Core Duo 2.33 GHz) such a  
simple build would take one second to execute.

If you go to GRADLE_HOME/samples/tutorial and execute:

gradle -bantChecksumfile checksum

How long does this take on your machine?

>
> Are there any thoughts of focusing on the aspect of performance?  
> What about
> gradle compiling the gradlefile into a .class file and using it in
> subsequent builds (if not changed of course)?

In general we want Gradle to be as fast as possible. Some aspects are  
it in our hand. For example the groovy startup time is something like  
0.3 seconds on my machine, compared to 0.1 seconds of Java. It looks  
like there are possibilities to improve this but I don't know what  
priority this has within the Groovy team. The other aspect not in our  
hands is the runtime performance of Groovy. This is a main focus of  
the Groovy guys right now and with 1.6 this will already improve  
significantly with still a lot of potential for improvement in the  
future. The third aspect is compile time speed. This will also be  
improved with 1.6. But of course we could use caching and timestamps  
to avoid this step altogether. Yet for a simple build script, I would  
think the compile time of the gradlefile is insignificant. The fourth  
aspect is the Gradle processing. Again I don't think this is  
significant. Anyway, we need to do some proper profiling of gradle  
builds to get a solid understanding here.

But six seconds for a simple build I consider as not acceptable.  I'm  
curios why it takes so long on your machine.

- Hans

>
> Thank you,
> Ittay
> --
> View this message in context: http://www.nabble.com/performance- 
> tp17504383p17504383.html
> Sent from the gradle-user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: performance

Ittay Dror
hdockter wrote
If you go to GRADLE_HOME/samples/tutorial and execute:

gradle -bantChecksumfile checksum

How long does this take on your machine?
6 seconds (i timed it with 'time gradle...')

I have a T61 (dual core 2.4G, 2GB memory), the OS is Ubuntu 8.04, java is 1.6.0.06 from sun.
hdockter wrote
But six seconds for a simple build I consider as not acceptable.  I'm  
curios why it takes so long on your machine.
Well, I would be glad to try and debug this, but I don't know where to start.

Ittay
Reply | Threaded
Open this post in threaded view
|

Re: performance

Ittay Dror
here is the output of running gradle (I wonder why it thinks there's no modern compiler, and why the core takes care of providing java compiler rather than the JavaPlugin):
No modern compiler.
Recursive: true
Buildfilename: antChecksumfile
No build sources found.
:: loading settings :: url = jar:file:/work/research/gradle-0.1.4/lib/ivy-2.0.0.beta2_20080305165542.jar!/org/apache/ivy/core/settings/ivysettings.xml
:: resolving dependencies :: org.gradle#build;SNAPSHOT
        confs: [build]
++++ Starting build for primary task: checksum
++ Loading Project objects
++ Configuring Project objects
Project=: evaluated.
++ Executing: checksum Recursive:true Startproject: :
Executing: :checksum
autoskipDependsfile Checksum: ddf6b3ebcc842bc529a4fd4acc4e5a37
pluginConventionfile Checksum: ca38a08ee66d17eb0555231e36f94ef4
pluginIntrofile Checksum: aa93992b7b9c1e07e03fa7fd27bd8de6
pluginConfigfile Checksum: bf34b3fbe0868419fecef862021c2bb4
datefile Checksum: a766e96e5fbdc2779ad03e6fd2b46f0f
projectApifile Checksum: d5a40ebab4616c8098be21213b8ae3fb

BUILD SUCCESSFUL

Total time: 3 seconds

real 0m4.861s
user 0m8.041s
sys 0m0.216s
Reply | Threaded
Open this post in threaded view
|

Re: performance

hans_d
Administrator
In reply to this post by Ittay Dror

On May 28, 2008, at 8:59 AM, Ittay Dror wrote:

>
>
> hdockter wrote:
>>
>> If you go to GRADLE_HOME/samples/tutorial and execute:
>>
>> gradle -bantChecksumfile checksum
>>
>> How long does this take on your machine?
>>
> 6 seconds (i timed it with 'time gradle...')
>
> I have a T61 (dual core 2.4G, 2GB memory), the OS is Ubuntu 8.04,  
> java is
> 1.6.0.06 from sun.
I have to correct myself. Using the time command I have an execution  
time on my machine of 2 seconds.

>
> hdockter wrote:
>>
>>
>> But six seconds for a simple build I consider as not acceptable.  I'm
>> curios why it takes so long on your machine.
>>
>
> Well, I would be glad to try and debug this, but I don't know where to
> start.
I have attached a zip. These zip contains a Java and Groovy class  
printing hello. Could you execute:

time groovy HelloGroovy.groovy
(My machine: 1.1 seconds)

time java -cp .:path_to_groovy-all_jar HelloGroovy
(My machine: 0.35 seconds)

time java HelloJava
(My machine: 0.1 seconds)

- Hans

>
> Ittay
> --
> View this message in context: http://www.nabble.com/performance- 
> tp17504383p17506309.html
> Sent from the gradle-user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
--
Hans Dockter
Gradle Project lead
http://www.gradle.org









---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

perf.zip (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: performance

Ittay Dror

hdockter wrote
time groovy HelloGroovy.groovy
(My machine: 1.1 seconds)

time java -cp .:path_to_groovy-all_jar HelloGroovy
(My machine: 0.35 seconds)

time java HelloJava
(My machine: 0.1 seconds)
(note: using 'groovy' means running /usr/bin/groovy which is an ubuntu package of groovy 1.5.4)

/tmp/perf > time groovy HelloGroovy.groovy
hello

real 0m1.034s
user 0m1.184s
sys 0m0.084s
/tmp/perf > time java -cp .:/work/research/gradle-0.1.4/lib/groovy-all-1.5.5.jar HelloGroovy
hello

real 0m0.788s
user 0m0.640s
sys 0m0.028s
/tmp/perf > time java HelloJava
Hello

real 0m0.150s
user 0m0.088s
sys 0m0.028s


So it looks like using the groovy jar in gradle is what is causing the slowdown. When running the 'groovy' command (first test), this is what it does:
exec /usr/lib/jvm/java-6-sun-1.6.0.06/bin/java -classpath /usr/share/groovy/lib/groovy-1.5.4.jar -Dscript.name=/usr/bin/groovy -Dprogram.name=groovy -Dgroovy.starter.conf=/usr/share/groovy/conf/groovy-starter.conf -Dgroovy.home=/usr/share/groovy -Dtools.jar=/usr/lib/jvm/java-6-sun-1.6.0.06/lib/tools.jar org.codehaus.groovy.tools.GroovyStarter --main groovy.ui.GroovyMain --conf /usr/share/groovy/conf/groovy-starter.conf --classpath . HelloGroovy.groovy


Reply | Threaded
Open this post in threaded view
|

Re: performance

hans_d
Administrator

On May 28, 2008, at 1:06 PM, Ittay Dror wrote:

>
>
>
> hdockter wrote:
>>
>> time groovy HelloGroovy.groovy
>> (My machine: 1.1 seconds)
>>
>> time java -cp .:path_to_groovy-all_jar HelloGroovy
>> (My machine: 0.35 seconds)
>>
>> time java HelloJava
>> (My machine: 0.1 seconds)
>>
> (note: using 'groovy' means running /usr/bin/groovy which is an ubuntu
> package of groovy 1.5.4)
>
> /tmp/perf > time groovy HelloGroovy.groovy
> hello
>
> real 0m1.034s
> user 0m1.184s
> sys 0m0.084s
> /tmp/perf > time java -cp
> .:/work/research/gradle-0.1.4/lib/groovy-all-1.5.5.jar HelloGroovy
> hello
>
> real 0m0.788s
> user 0m0.640s
> sys 0m0.028s
> /tmp/perf > time java HelloJava
> Hello
>
> real 0m0.150s
> user 0m0.088s
> sys 0m0.028s
>
>
> So it looks like using the groovy jar in gradle is what is causing the
> slowdown. When running the 'groovy' command (first test), this is  
> what it
> does:
> exec /usr/lib/jvm/java-6-sun-1.6.0.06/bin/java -classpath
> /usr/share/groovy/lib/groovy-1.5.4.jar -Dscript.name=/usr/bin/groovy
> -Dprogram.name=groovy
> -Dgroovy.starter.conf=/usr/share/groovy/conf/groovy-starter.conf
> -Dgroovy.home=/usr/share/groovy
> -Dtools.jar=/usr/lib/jvm/java-6-sun-1.6.0.06/lib/tools.jar
> org.codehaus.groovy.tools.GroovyStarter --main groovy.ui.GroovyMain  
> --conf
> /usr/share/groovy/conf/groovy-starter.conf --classpath .  
> HelloGroovy.groovy

In the first example we have groovy startup-time plus compile time,  
in the second only startup-time. The Groovy startup-time is  
significant as a lot of classloading is happening. As a side note:  
The JRuby startup time is a couple of seconds, although they have  
found a way to improve this in there next release.  It is interesting  
that the startup time is twice as long on your machine, although you  
have a faster processor. Yet this is still not the complete story of  
the slow performance of your gradle build. What I want to do  
tomorrow, is to upload a snapshot version of Gradle which prints  
timing information when started in debug mode. That way we should  
learn about the other bottlenecks. I will ping you when I've uploaded  
the new snapshot version.

- Hans

>
> --
> View this message in context: http://www.nabble.com/performance- 
> tp17504383p17510256.html
> Sent from the gradle-user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: performance

hans_d
Administrator
In reply to this post by Ittay Dror

On May 28, 2008, at 9:23 AM, Ittay Dror wrote:

>
> here is the output of running gradle (I wonder why it thinks  
> there's no
> modern compiler, and why the core takes care of providing java  
> compiler
> rather than the JavaPlugin):

This is a valid point. This is related to how we do classloading  
right now. This will probably be improved with the new plugin system.

- Hans

> No modern compiler.
> Recursive: true
> Buildfilename: antChecksumfile
> No build sources found.
> :: loading settings :: url =
> jar:file:/work/research/gradle-0.1.4/lib/
> ivy-2.0.0.beta2_20080305165542.jar!/org/apache/ivy/core/settings/
> ivysettings.xml
> :: resolving dependencies :: org.gradle#build;SNAPSHOT
> confs: [build]
> ++++ Starting build for primary task: checksum
> ++ Loading Project objects
> ++ Configuring Project objects
> Project=: evaluated.
> ++ Executing: checksum Recursive:true Startproject: :
> Executing: :checksum
> autoskipDependsfile Checksum: ddf6b3ebcc842bc529a4fd4acc4e5a37
> pluginConventionfile Checksum: ca38a08ee66d17eb0555231e36f94ef4
> pluginIntrofile Checksum: aa93992b7b9c1e07e03fa7fd27bd8de6
> pluginConfigfile Checksum: bf34b3fbe0868419fecef862021c2bb4
> datefile Checksum: a766e96e5fbdc2779ad03e6fd2b46f0f
> projectApifile Checksum: d5a40ebab4616c8098be21213b8ae3fb
>
> BUILD SUCCESSFUL
>
> Total time: 3 seconds
>
> real 0m4.861s
> user 0m8.041s
> sys 0m0.216s
>
> --
> View this message in context: http://www.nabble.com/performance- 
> tp17504383p17506594.html
> Sent from the gradle-user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: performance

hans_d
Administrator
In reply to this post by hans_d

On May 28, 2008, at 3:10 PM, Hans Dockter wrote:

>
> On May 28, 2008, at 1:06 PM, Ittay Dror wrote:
>
>>
>>
>>
>> hdockter wrote:
>>>
>>> time groovy HelloGroovy.groovy
>>> (My machine: 1.1 seconds)
>>>
>>> time java -cp .:path_to_groovy-all_jar HelloGroovy
>>> (My machine: 0.35 seconds)
>>>
>>> time java HelloJava
>>> (My machine: 0.1 seconds)
>>>
>> (note: using 'groovy' means running /usr/bin/groovy which is an  
>> ubuntu
>> package of groovy 1.5.4)
>>
>> /tmp/perf > time groovy HelloGroovy.groovy
>> hello
>>
>> real 0m1.034s
>> user 0m1.184s
>> sys 0m0.084s
>> /tmp/perf > time java -cp
>> .:/work/research/gradle-0.1.4/lib/groovy-all-1.5.5.jar HelloGroovy
>> hello
>>
>> real 0m0.788s
>> user 0m0.640s
>> sys 0m0.028s
>> /tmp/perf > time java HelloJava
>> Hello
>>
>> real 0m0.150s
>> user 0m0.088s
>> sys 0m0.028s
>>
>>
>> So it looks like using the groovy jar in gradle is what is causing  
>> the
>> slowdown. When running the 'groovy' command (first test), this is  
>> what it
>> does:
>> exec /usr/lib/jvm/java-6-sun-1.6.0.06/bin/java -classpath
>> /usr/share/groovy/lib/groovy-1.5.4.jar -Dscript.name=/usr/bin/groovy
>> -Dprogram.name=groovy
>> -Dgroovy.starter.conf=/usr/share/groovy/conf/groovy-starter.conf
>> -Dgroovy.home=/usr/share/groovy
>> -Dtools.jar=/usr/lib/jvm/java-6-sun-1.6.0.06/lib/tools.jar
>> org.codehaus.groovy.tools.GroovyStarter --main  
>> groovy.ui.GroovyMain --conf
>> /usr/share/groovy/conf/groovy-starter.conf --classpath .  
>> HelloGroovy.groovy
>
> In the first example we have groovy startup-time plus compile time,  
> in the second only startup-time. The Groovy startup-time is  
> significant as a lot of classloading is happening. As a side note:  
> The JRuby startup time is a couple of seconds, although they have  
> found a way to improve this in there next release.  It is  
> interesting that the startup time is twice as long on your machine,  
> although you have a faster processor. Yet this is still not the  
> complete story of the slow performance of your gradle build. What I  
> want to do tomorrow, is to upload a snapshot version of Gradle  
> which prints timing information when started in debug mode. That  
> way we should learn about the other bottlenecks. I will ping you  
> when I've uploaded the new snapshot version.

I haven't produced the new snapshot yet. I'm out of office until  
Sunday, so it will be hopefully Monday.

- Hans

>
> - Hans
>
>>
>> --
>> View this message in context: http://www.nabble.com/performance- 
>> tp17504383p17510256.html
>> Sent from the gradle-user mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: performance

Ittay Dror
Hi,
hdockter wrote
I haven't produced the new snapshot yet. I'm out of office until  
Sunday, so it will be hopefully Monday.
Any updates?

For testing, attached are the gradlefile I use and the output of running gradle (the first line shows the command I run). It looks like groovy's startup is 0.7 seconds and that gradle's bootstrapping takes 2.2 seconds. gradlefileoutput

Ittay

Reply | Threaded
Open this post in threaded view
|

Re: performance

hans_d
Administrator
Hi Ittay,

On Jun 10, 2008, at 9:24 AM, Ittay Dror wrote:

>
> Hi,
>
> hdockter wrote:
>>
>> I haven't produced the new snapshot yet. I'm out of office until
>> Sunday, so it will be hopefully Monday.
>>
>
> Any updates?

Finally I have submitted it. I know that it is the wrong monday ;).  
Sorry.

If you start Gradle in debug mode (-d) search for log output that  
starts with 'Timing:'.

- Hans

>
> For testing, attached are the gradlefile I use and the output of  
> running
> gradle (the first line shows the command I run). It looks like  
> groovy's
> startup is 0.7 seconds and that gradle's bootstrapping takes 2.2  
> seconds.
> http://www.nabble.com/file/p17749311/gradlefile gradlefile
> http://www.nabble.com/file/p17749311/output output
>
> Ittay
>
>
> --
> View this message in context: http://www.nabble.com/performance- 
> tp17504383p17749311.html
> Sent from the gradle-user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: performance

hans_d
Administrator

On Jun 10, 2008, at 11:49 AM, Hans Dockter wrote:

> Hi Ittay,
>
> On Jun 10, 2008, at 9:24 AM, Ittay Dror wrote:
>
>>
>> Hi,
>>
>> hdockter wrote:
>>>
>>> I haven't produced the new snapshot yet. I'm out of office until
>>> Sunday, so it will be hopefully Monday.
>>>
>>
>> Any updates?
>
> Finally I have submitted it. I know that it is the wrong monday ;).  
> Sorry.
>
> If you start Gradle in debug mode (-d) search for log output that  
> starts with 'Timing:'.

I have submitted it to both the release branch and trunk.

If you want to build you might use the skip properties to accelerate it:

gradle -Dskip.userguide -Dskip.javadoc -Dskip.test -Dskip.integTest  
clean dists

You might also use a SNAPSHOT from our CI-Servers.

For example: http://teamcity.jetbrains.com/viewLog.html?
buildId=11818&buildTypeId=bt113&tab=artifacts

There is now a bin distribution without samples and source.

- Hans



>
> - Hans
>
>>
>> For testing, attached are the gradlefile I use and the output of  
>> running
>> gradle (the first line shows the command I run). It looks like  
>> groovy's
>> startup is 0.7 seconds and that gradle's bootstrapping takes 2.2  
>> seconds.
>> http://www.nabble.com/file/p17749311/gradlefile gradlefile
>> http://www.nabble.com/file/p17749311/output output
>>
>> Ittay
>>
>>
>> --
>> View this message in context: http://www.nabble.com/performance- 
>> tp17504383p17749311.html
>> Sent from the gradle-user mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: performance

Ittay Dror


Hans Dockter wrote:

On Jun 10, 2008, at 11:49 AM, Hans Dockter wrote:

Hi Ittay,

On Jun 10, 2008, at 9:24 AM, Ittay Dror wrote:


Hi,

hdockter wrote:

I haven't produced the new snapshot yet. I'm out of office until
Sunday, so it will be hopefully Monday.


Any updates?

Finally I have submitted it. I know that it is the wrong monday ;). Sorry.

If you start Gradle in debug mode (-d) search for log output that starts with 'Timing:'.

I have submitted it to both the release branch and trunk.

If you want to build you might use the skip properties to accelerate it:

gradle -Dskip.userguide -Dskip.javadoc -Dskip.test -Dskip.integTest clean dists

You might also use a SNAPSHOT from our CI-Servers.

For example: http://teamcity.jetbrains.com/viewLog.html?buildId=11818&buildTypeId=bt113&tab=artifacts

There is now a bin distribution without samples and source.

Trying to build I get this:
Can't access svn working copy. Maybe this is not an svn project or the codehausUserName/password property is not set.
                Releasing won't be possible. It is assumed that this isTrunk is true.

Build aborted anormally.  Run with -s option to get stacktrace. Run with -d option to get all debug info including stacktrace. Run (additionally) with -f option to get the full (very verbose) stacktrace
Exception: org.gradle.api.GradleScriptException: groovy.lang.MissingMethodException: No signature of method: org.gradle.api.tasks.bundling.Bundle.zip() is applicable for argument types: (java.util.LinkedHashMap) values: {["classifier":"all"]} Buildscript=gradlefile in line(s): 185 182

and trying to download: http://teamcity.jetbrains.com/repository/download/bt113/11818:id/gradle-0.2-080610135404%2B0400-bin.zip, I get this:
Artifact does not exist: gradle-0.2-080610135404 0400-bin.zip
- Hans




- Hans


For testing, attached are the gradlefile I use and the output of running
gradle (the first line shows the command I run). It looks like groovy's
startup is 0.7 seconds and that gradle's bootstrapping takes 2.2 seconds.
http://www.nabble.com/file/p17749311/gradlefile gradlefile
http://www.nabble.com/file/p17749311/output output

Ittay


-- 
View this message in context: http://www.nabble.com/performance-tp17504383p17749311.html
Sent from the gradle-user mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email



--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email



-- 
--
Ittay Dror [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: performance

hans_d
Administrator

On Jun 10, 2008, at 12:27 PM, Ittay Dror wrote:

>
>
> Hans Dockter wrote:
>>
>>
>> On Jun 10, 2008, at 11:49 AM, Hans Dockter wrote:
>>
>>> Hi Ittay,
>>>
>>> On Jun 10, 2008, at 9:24 AM, Ittay Dror wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> hdockter wrote:
>>>>>
>>>>> I haven't produced the new snapshot yet. I'm out of office until
>>>>> Sunday, so it will be hopefully Monday.
>>>>>
>>>>
>>>> Any updates?
>>>
>>> Finally I have submitted it. I know that it is the wrong  
>>> monday ;). Sorry.
>>>
>>> If you start Gradle in debug mode (-d) search for log output that  
>>> starts with 'Timing:'.
>>
>> I have submitted it to both the release branch and trunk.
>>
>> If you want to build you might use the skip properties to  
>> accelerate it:
>>
>> gradle -Dskip.userguide -Dskip.javadoc -Dskip.test -
>> Dskip.integTest clean dists
>>
>> You might also use a SNAPSHOT from our CI-Servers.
>>
>> For example: http://teamcity.jetbrains.com/viewLog.html?
>> buildId=11818&buildTypeId=bt113&tab=artifacts
>>
>> There is now a bin distribution without samples and source.
>>
> Trying to build I get this:
> Can't access svn working copy. Maybe this is not an svn project or  
> the codehausUserName/password property is not set.
>                 Releasing won't be possible. It is assumed that  
> this isTrunk is true.
>
> Build aborted anormally.  Run with -s option to get stacktrace. Run  
> with -d option to get all debug info including stacktrace. Run  
> (additionally) with -f option to get the full (very verbose)  
> stacktrace
> Exception: org.gradle.api.GradleScriptException:  
> groovy.lang.MissingMethodException: No signature of method:  
> org.gradle.api.tasks.bundling.Bundle.zip() is applicable for  
> argument types: (java.util.LinkedHashMap) values:  
> {["classifier":"all"]} Buildscript=gradlefile in line(s): 185 182

This is our hen-egg problem. The Gradle version in svn needs a newer  
version than 0.1.4 to be build. With the help of the gradle wrapper  
you can compile as it is (as a valid version to compile Gradle is in  
svn).

Just type:

./gradlew -Dskip.userguide -Dskip.javadoc -Dskip.test -
Dskip.integTest clean dists

I'm going to upload a snapshot dist to our codehaus snapshot  
repository as well.

It is also time to create a developer page in our Wiki.

>
>
> and trying to download: http://teamcity.jetbrains.com/repository/ 
> download/bt113/11818:id/gradle-0.2-080610135404%2B0400-bin.zip, I  
> get this:
> Artifact does not exist: gradle-0.2-080610135404 0400-bin.zip

This looks like a problem with our CI server.

- Hans

>
>> - Hans
>>
>>
>>
>>>
>>> - Hans
>>>
>>>>
>>>> For testing, attached are the gradlefile I use and the output of  
>>>> running
>>>> gradle (the first line shows the command I run). It looks like  
>>>> groovy's
>>>> startup is 0.7 seconds and that gradle's bootstrapping takes 2.2  
>>>> seconds.
>>>> http://www.nabble.com/file/p17749311/gradlefile gradlefile
>>>> http://www.nabble.com/file/p17749311/output output
>>>>
>>>> Ittay
>>>>
>>>>
>>>> --
>>>> View this message in context: http://www.nabble.com/performance- 
>>>> tp17504383p17749311.html
>>>> Sent from the gradle-user mailing list archive at Nabble.com.
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>     http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>
>>> --
>>> Hans Dockter
>>> Gradle Project lead
>>> http://www.gradle.org
>>>
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>> --
>> Hans Dockter
>> Gradle Project lead
>> http://www.gradle.org
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
> -- -- Ittay Dror <[hidden email]>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: performance

hans_d
Administrator

On Jun 10, 2008, at 12:45 PM, Hans Dockter wrote:

>
> On Jun 10, 2008, at 12:27 PM, Ittay Dror wrote:
>
>>
>>
>> Hans Dockter wrote:
>>>
>>>
>>> On Jun 10, 2008, at 11:49 AM, Hans Dockter wrote:
>>>
>>>> Hi Ittay,
>>>>
>>>> On Jun 10, 2008, at 9:24 AM, Ittay Dror wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> hdockter wrote:
>>>>>>
>>>>>> I haven't produced the new snapshot yet. I'm out of office until
>>>>>> Sunday, so it will be hopefully Monday.
>>>>>>
>>>>>
>>>>> Any updates?
>>>>
>>>> Finally I have submitted it. I know that it is the wrong  
>>>> monday ;). Sorry.
>>>>
>>>> If you start Gradle in debug mode (-d) search for log output  
>>>> that starts with 'Timing:'.
>>>
>>> I have submitted it to both the release branch and trunk.
>>>
>>> If you want to build you might use the skip properties to  
>>> accelerate it:
>>>
>>> gradle -Dskip.userguide -Dskip.javadoc -Dskip.test -
>>> Dskip.integTest clean dists
>>>
>>> You might also use a SNAPSHOT from our CI-Servers.
>>>
>>> For example: http://teamcity.jetbrains.com/viewLog.html?
>>> buildId=11818&buildTypeId=bt113&tab=artifacts
>>>
>>> There is now a bin distribution without samples and source.
>>>
>> Trying to build I get this:
>> Can't access svn working copy. Maybe this is not an svn project or  
>> the codehausUserName/password property is not set.
>>                 Releasing won't be possible. It is assumed that  
>> this isTrunk is true.
>>
>> Build aborted anormally.  Run with -s option to get stacktrace.  
>> Run with -d option to get all debug info including stacktrace. Run  
>> (additionally) with -f option to get the full (very verbose)  
>> stacktrace
>> Exception: org.gradle.api.GradleScriptException:  
>> groovy.lang.MissingMethodException: No signature of method:  
>> org.gradle.api.tasks.bundling.Bundle.zip() is applicable for  
>> argument types: (java.util.LinkedHashMap) values:  
>> {["classifier":"all"]} Buildscript=gradlefile in line(s): 185 182
>
> This is our hen-egg problem. The Gradle version in svn needs a  
> newer version than 0.1.4 to be build. With the help of the gradle  
> wrapper you can compile as it is (as a valid version to compile  
> Gradle is in svn).
>
> Just type:
>
> ./gradlew -Dskip.userguide -Dskip.javadoc -Dskip.test -
> Dskip.integTest clean dists
>
> I'm going to upload a snapshot dist to our codehaus snapshot  
> repository as well.

https://dav.codehaus.org/snapshots.dist/gradle/ 
gradle-0.1.5-080610123954+0200-bin.zip

>
> It is also time to create a developer page in our Wiki.
>
>>
>>
>> and trying to download: http://teamcity.jetbrains.com/repository/ 
>> download/bt113/11818:id/gradle-0.2-080610135404%2B0400-bin.zip, I  
>> get this:
>> Artifact does not exist: gradle-0.2-080610135404 0400-bin.zip
>
> This looks like a problem with our CI server.
>
> - Hans
>
>>
>>> - Hans
>>>
>>>
>>>
>>>>
>>>> - Hans
>>>>
>>>>>
>>>>> For testing, attached are the gradlefile I use and the output  
>>>>> of running
>>>>> gradle (the first line shows the command I run). It looks like  
>>>>> groovy's
>>>>> startup is 0.7 seconds and that gradle's bootstrapping takes  
>>>>> 2.2 seconds.
>>>>> http://www.nabble.com/file/p17749311/gradlefile gradlefile
>>>>> http://www.nabble.com/file/p17749311/output output
>>>>>
>>>>> Ittay
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context: http://www.nabble.com/performance- 
>>>>> tp17504383p17749311.html
>>>>> Sent from the gradle-user mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe from this list, please visit:
>>>>>
>>>>>     http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>
>>>> --
>>>> Hans Dockter
>>>> Gradle Project lead
>>>> http://www.gradle.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>
>>> --
>>> Hans Dockter
>>> Gradle Project lead
>>> http://www.gradle.org
>>>
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>> -- -- Ittay Dror <[hidden email]>
>
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: performance

Ittay Dror
In reply to this post by hans_d
Here are the results:
 > gradle -u -n -d -bgradlefile2 resources | grep Timing
13:56:58.634 [main] DEBUG o.g.initialization.ProjectsLoader - Timing:
Loading projects took: 0.021 secs
13:56:58.903 [main] DEBUG o.g.a.i.project.BuildScriptProcessor - Timing:
Parsing the build script took 0.254 secs
13:56:59.785 [main] DEBUG o.g.a.i.project.BuildScriptProcessor - Timing:
Running the build script took 0.876 secs
13:56:59.805 [main] DEBUG o.g.a.i.project.DefaultProject - Timing:
Project evaluation took 1.166 secs
13:56:59.809 [main] DEBUG o.g.configuration.BuildConfigurer - Timing:
Configuring projects took 1.175 secs


Hans Dockter wrote:

>
> On Jun 10, 2008, at 12:27 PM, Ittay Dror wrote:
>
>>
>>
>> Hans Dockter wrote:
>>>
>>>
>>> On Jun 10, 2008, at 11:49 AM, Hans Dockter wrote:
>>>
>>>> Hi Ittay,
>>>>
>>>> On Jun 10, 2008, at 9:24 AM, Ittay Dror wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> hdockter wrote:
>>>>>>
>>>>>> I haven't produced the new snapshot yet. I'm out of office until
>>>>>> Sunday, so it will be hopefully Monday.
>>>>>>
>>>>>
>>>>> Any updates?
>>>>
>>>> Finally I have submitted it. I know that it is the wrong monday ;).
>>>> Sorry.
>>>>
>>>> If you start Gradle in debug mode (-d) search for log output that
>>>> starts with 'Timing:'.
>>>
>>> I have submitted it to both the release branch and trunk.
>>>
>>> If you want to build you might use the skip properties to accelerate
>>> it:
>>>
>>> gradle -Dskip.userguide -Dskip.javadoc -Dskip.test -Dskip.integTest
>>> clean dists
>>>
>>> You might also use a SNAPSHOT from our CI-Servers.
>>>
>>> For example:
>>> http://teamcity.jetbrains.com/viewLog.html?buildId=11818&buildTypeId=bt113&tab=artifacts 
>>>
>>>
>>> There is now a bin distribution without samples and source.
>>>
>> Trying to build I get this:
>> Can't access svn working copy. Maybe this is not an svn project or
>> the codehausUserName/password property is not set.
>>                 Releasing won't be possible. It is assumed that this
>> isTrunk is true.
>>
>> Build aborted anormally.  Run with -s option to get stacktrace. Run
>> with -d option to get all debug info including stacktrace. Run
>> (additionally) with -f option to get the full (very verbose) stacktrace
>> Exception: org.gradle.api.GradleScriptException:
>> groovy.lang.MissingMethodException: No signature of method:
>> org.gradle.api.tasks.bundling.Bundle.zip() is applicable for argument
>> types: (java.util.LinkedHashMap) values: {["classifier":"all"]}
>> Buildscript=gradlefile in line(s): 185 182
>
> This is our hen-egg problem. The Gradle version in svn needs a newer
> version than 0.1.4 to be build. With the help of the gradle wrapper
> you can compile as it is (as a valid version to compile Gradle is in
> svn).
>
> Just type:
>
> ./gradlew -Dskip.userguide -Dskip.javadoc -Dskip.test -Dskip.integTest
> clean dists
>
> I'm going to upload a snapshot dist to our codehaus snapshot
> repository as well.
>
> It is also time to create a developer page in our Wiki.
>
>>
>>
>> and trying to download:
>> http://teamcity.jetbrains.com/repository/download/bt113/11818:id/gradle-0.2-080610135404%2B0400-bin.zip,
>> I get this:
>> Artifact does not exist: gradle-0.2-080610135404 0400-bin.zip
>
> This looks like a problem with our CI server.
>
> - Hans
>
>>
>>> - Hans
>>>
>>>
>>>
>>>>
>>>> - Hans
>>>>
>>>>>
>>>>> For testing, attached are the gradlefile I use and the output of
>>>>> running
>>>>> gradle (the first line shows the command I run). It looks like
>>>>> groovy's
>>>>> startup is 0.7 seconds and that gradle's bootstrapping takes 2.2
>>>>> seconds.
>>>>> http://www.nabble.com/file/p17749311/gradlefile gradlefile
>>>>> http://www.nabble.com/file/p17749311/output output
>>>>>
>>>>> Ittay
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/performance-tp17504383p17749311.html
>>>>> Sent from the gradle-user mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe from this list, please visit:
>>>>>
>>>>>     http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>
>>>> --
>>>> Hans Dockter
>>>> Gradle Project lead
>>>> http://www.gradle.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>
>>> --
>>> Hans Dockter
>>> Gradle Project lead
>>> http://www.gradle.org
>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>> -- -- Ittay Dror <[hidden email]>
>
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

--
--
Ittay Dror <[hidden email]>


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: performance

hans_d
Administrator
Hi Ittay,

On Jun 10, 2008, at 12:57 PM, Ittay Dror wrote:

> Here are the results:
> > gradle -u -n -d -bgradlefile2 resources | grep Timing
> 13:56:58.634 [main] DEBUG o.g.initialization.ProjectsLoader -  
> Timing: Loading projects took: 0.021 secs
> 13:56:58.903 [main] DEBUG o.g.a.i.project.BuildScriptProcessor -  
> Timing: Parsing the build script took 0.254 secs
> 13:56:59.785 [main] DEBUG o.g.a.i.project.BuildScriptProcessor -  
> Timing: Running the build script took 0.876 secs
> 13:56:59.805 [main] DEBUG o.g.a.i.project.DefaultProject - Timing:  
> Project evaluation took 1.166 secs
> 13:56:59.809 [main] DEBUG o.g.configuration.BuildConfigurer -  
> Timing: Configuring projects took 1.175 secs

I have observed something similar. It seems strange to me that  
running the build script takes that long. This is not the build  
execution after all, just executing the script to configure the build.

I have to investigate.

Thanks

- Hans

>
>
> Hans Dockter wrote:
>>
>> On Jun 10, 2008, at 12:27 PM, Ittay Dror wrote:
>>
>>>
>>>
>>> Hans Dockter wrote:
>>>>
>>>>
>>>> On Jun 10, 2008, at 11:49 AM, Hans Dockter wrote:
>>>>
>>>>> Hi Ittay,
>>>>>
>>>>> On Jun 10, 2008, at 9:24 AM, Ittay Dror wrote:
>>>>>
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> hdockter wrote:
>>>>>>>
>>>>>>> I haven't produced the new snapshot yet. I'm out of office until
>>>>>>> Sunday, so it will be hopefully Monday.
>>>>>>>
>>>>>>
>>>>>> Any updates?
>>>>>
>>>>> Finally I have submitted it. I know that it is the wrong  
>>>>> monday ;). Sorry.
>>>>>
>>>>> If you start Gradle in debug mode (-d) search for log output  
>>>>> that starts with 'Timing:'.
>>>>
>>>> I have submitted it to both the release branch and trunk.
>>>>
>>>> If you want to build you might use the skip properties to  
>>>> accelerate it:
>>>>
>>>> gradle -Dskip.userguide -Dskip.javadoc -Dskip.test -
>>>> Dskip.integTest clean dists
>>>>
>>>> You might also use a SNAPSHOT from our CI-Servers.
>>>>
>>>> For example: http://teamcity.jetbrains.com/viewLog.html?
>>>> buildId=11818&buildTypeId=bt113&tab=artifacts
>>>>
>>>> There is now a bin distribution without samples and source.
>>>>
>>> Trying to build I get this:
>>> Can't access svn working copy. Maybe this is not an svn project  
>>> or the codehausUserName/password property is not set.
>>>                 Releasing won't be possible. It is assumed that  
>>> this isTrunk is true.
>>>
>>> Build aborted anormally.  Run with -s option to get stacktrace.  
>>> Run with -d option to get all debug info including stacktrace.  
>>> Run (additionally) with -f option to get the full (very verbose)  
>>> stacktrace
>>> Exception: org.gradle.api.GradleScriptException:  
>>> groovy.lang.MissingMethodException: No signature of method:  
>>> org.gradle.api.tasks.bundling.Bundle.zip() is applicable for  
>>> argument types: (java.util.LinkedHashMap) values:  
>>> {["classifier":"all"]} Buildscript=gradlefile in line(s): 185 182
>>
>> This is our hen-egg problem. The Gradle version in svn needs a  
>> newer version than 0.1.4 to be build. With the help of the gradle  
>> wrapper you can compile as it is (as a valid version to compile  
>> Gradle is in svn).
>>
>> Just type:
>>
>> ./gradlew -Dskip.userguide -Dskip.javadoc -Dskip.test -
>> Dskip.integTest clean dists
>>
>> I'm going to upload a snapshot dist to our codehaus snapshot  
>> repository as well.
>>
>> It is also time to create a developer page in our Wiki.
>>
>>>
>>>
>>> and trying to download: http://teamcity.jetbrains.com/repository/ 
>>> download/bt113/11818:id/gradle-0.2-080610135404%2B0400-bin.zip, I  
>>> get this:
>>> Artifact does not exist: gradle-0.2-080610135404 0400-bin.zip
>>
>> This looks like a problem with our CI server.
>>
>> - Hans
>>
>>>
>>>> - Hans
>>>>
>>>>
>>>>
>>>>>
>>>>> - Hans
>>>>>
>>>>>>
>>>>>> For testing, attached are the gradlefile I use and the output  
>>>>>> of running
>>>>>> gradle (the first line shows the command I run). It looks like  
>>>>>> groovy's
>>>>>> startup is 0.7 seconds and that gradle's bootstrapping takes  
>>>>>> 2.2 seconds.
>>>>>> http://www.nabble.com/file/p17749311/gradlefile gradlefile
>>>>>> http://www.nabble.com/file/p17749311/output output
>>>>>>
>>>>>> Ittay
>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context: http://www.nabble.com/ 
>>>>>> performance-tp17504383p17749311.html
>>>>>> Sent from the gradle-user mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> ----
>>>>>> To unsubscribe from this list, please visit:
>>>>>>
>>>>>>     http://xircles.codehaus.org/manage_email
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Hans Dockter
>>>>> Gradle Project lead
>>>>> http://www.gradle.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>
>>>> --
>>>> Hans Dockter
>>>> Gradle Project lead
>>>> http://www.gradle.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>
>>> -- -- Ittay Dror <[hidden email]>
>>
>> --
>> Hans Dockter
>> Gradle Project lead
>> http://www.gradle.org
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
> --
> --
> Ittay Dror <[hidden email]>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: performance

hans_d
Administrator

On Jun 10, 2008, at 1:13 PM, Hans Dockter wrote:

> Hi Ittay,
>
> On Jun 10, 2008, at 12:57 PM, Ittay Dror wrote:
>
>> Here are the results:
>> > gradle -u -n -d -bgradlefile2 resources | grep Timing
>> 13:56:58.634 [main] DEBUG o.g.initialization.ProjectsLoader -  
>> Timing: Loading projects took: 0.021 secs
>> 13:56:58.903 [main] DEBUG o.g.a.i.project.BuildScriptProcessor -  
>> Timing: Parsing the build script took 0.254 secs
>> 13:56:59.785 [main] DEBUG o.g.a.i.project.BuildScriptProcessor -  
>> Timing: Running the build script took 0.876 secs
>> 13:56:59.805 [main] DEBUG o.g.a.i.project.DefaultProject - Timing:  
>> Project evaluation took 1.166 secs
>> 13:56:59.809 [main] DEBUG o.g.configuration.BuildConfigurer -  
>> Timing: Configuring projects took 1.175 secs
>
> I have observed something similar. It seems strange to me that  
> running the build script takes that long. This is not the build  
> execution after all, just executing the script to configure the build.
>
> I have to investigate.

There is an issue to track this: http://jira.codehaus.org/browse/ 
GRADLE-114

>
> Thanks
>
> - Hans
>
>>
>>
>> Hans Dockter wrote:
>>>
>>> On Jun 10, 2008, at 12:27 PM, Ittay Dror wrote:
>>>
>>>>
>>>>
>>>> Hans Dockter wrote:
>>>>>
>>>>>
>>>>> On Jun 10, 2008, at 11:49 AM, Hans Dockter wrote:
>>>>>
>>>>>> Hi Ittay,
>>>>>>
>>>>>> On Jun 10, 2008, at 9:24 AM, Ittay Dror wrote:
>>>>>>
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> hdockter wrote:
>>>>>>>>
>>>>>>>> I haven't produced the new snapshot yet. I'm out of office  
>>>>>>>> until
>>>>>>>> Sunday, so it will be hopefully Monday.
>>>>>>>>
>>>>>>>
>>>>>>> Any updates?
>>>>>>
>>>>>> Finally I have submitted it. I know that it is the wrong  
>>>>>> monday ;). Sorry.
>>>>>>
>>>>>> If you start Gradle in debug mode (-d) search for log output  
>>>>>> that starts with 'Timing:'.
>>>>>
>>>>> I have submitted it to both the release branch and trunk.
>>>>>
>>>>> If you want to build you might use the skip properties to  
>>>>> accelerate it:
>>>>>
>>>>> gradle -Dskip.userguide -Dskip.javadoc -Dskip.test -
>>>>> Dskip.integTest clean dists
>>>>>
>>>>> You might also use a SNAPSHOT from our CI-Servers.
>>>>>
>>>>> For example: http://teamcity.jetbrains.com/viewLog.html?
>>>>> buildId=11818&buildTypeId=bt113&tab=artifacts
>>>>>
>>>>> There is now a bin distribution without samples and source.
>>>>>
>>>> Trying to build I get this:
>>>> Can't access svn working copy. Maybe this is not an svn project  
>>>> or the codehausUserName/password property is not set.
>>>>                 Releasing won't be possible. It is assumed that  
>>>> this isTrunk is true.
>>>>
>>>> Build aborted anormally.  Run with -s option to get stacktrace.  
>>>> Run with -d option to get all debug info including stacktrace.  
>>>> Run (additionally) with -f option to get the full (very verbose)  
>>>> stacktrace
>>>> Exception: org.gradle.api.GradleScriptException:  
>>>> groovy.lang.MissingMethodException: No signature of method:  
>>>> org.gradle.api.tasks.bundling.Bundle.zip() is applicable for  
>>>> argument types: (java.util.LinkedHashMap) values:  
>>>> {["classifier":"all"]} Buildscript=gradlefile in line(s): 185 182
>>>
>>> This is our hen-egg problem. The Gradle version in svn needs a  
>>> newer version than 0.1.4 to be build. With the help of the gradle  
>>> wrapper you can compile as it is (as a valid version to compile  
>>> Gradle is in svn).
>>>
>>> Just type:
>>>
>>> ./gradlew -Dskip.userguide -Dskip.javadoc -Dskip.test -
>>> Dskip.integTest clean dists
>>>
>>> I'm going to upload a snapshot dist to our codehaus snapshot  
>>> repository as well.
>>>
>>> It is also time to create a developer page in our Wiki.
>>>
>>>>
>>>>
>>>> and trying to download: http://teamcity.jetbrains.com/repository/ 
>>>> download/bt113/11818:id/gradle-0.2-080610135404%2B0400-bin.zip,  
>>>> I get this:
>>>> Artifact does not exist: gradle-0.2-080610135404 0400-bin.zip
>>>
>>> This looks like a problem with our CI server.
>>>
>>> - Hans
>>>
>>>>
>>>>> - Hans
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> - Hans
>>>>>>
>>>>>>>
>>>>>>> For testing, attached are the gradlefile I use and the output  
>>>>>>> of running
>>>>>>> gradle (the first line shows the command I run). It looks  
>>>>>>> like groovy's
>>>>>>> startup is 0.7 seconds and that gradle's bootstrapping takes  
>>>>>>> 2.2 seconds.
>>>>>>> http://www.nabble.com/file/p17749311/gradlefile gradlefile
>>>>>>> http://www.nabble.com/file/p17749311/output output
>>>>>>>
>>>>>>> Ittay
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> View this message in context: http://www.nabble.com/ 
>>>>>>> performance-tp17504383p17749311.html
>>>>>>> Sent from the gradle-user mailing list archive at Nabble.com.
>>>>>>>
>>>>>>>
>>>>>>> ----------------------------------------------------------------
>>>>>>> -----
>>>>>>> To unsubscribe from this list, please visit:
>>>>>>>
>>>>>>>     http://xircles.codehaus.org/manage_email
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Hans Dockter
>>>>>> Gradle Project lead
>>>>>> http://www.gradle.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> ----
>>>>>> To unsubscribe from this list, please visit:
>>>>>>
>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Hans Dockter
>>>>> Gradle Project lead
>>>>> http://www.gradle.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>
>>>> -- -- Ittay Dror <[hidden email]>
>>>
>>> --
>>> Hans Dockter
>>> Gradle Project lead
>>> http://www.gradle.org
>>>
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>> --
>> --
>> Ittay Dror <[hidden email]>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email