Search

2012-01-30 Thread Igor Drobiazko
The search functionality on Tapestry's home page provides unexpected results. I just searched for "release" and wondered about the result #4. I guess we should change it. -- Best regards, Igor Drobiazko http://tapestry5.de http://twitter.com/drobiazko

buildbot success in ASF Buildbot on tapestry-trunk

2012-01-30 Thread buildbot
The Buildbot has finished a build on builder tapestry-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tapestry-trunk/builds/48 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: isis_ubuntu Build Reason: scheduler Build Source Stamp:

Build failed in Jenkins: tapestry-trunk-freestyle #678

2012-01-30 Thread Apache Jenkins Server
See Changes: [hlship] Update the build to generate and upload PGP signatures along with the MD5 checksums for the sources and javadoc artifacts -- Started by an SCM change Building remot

Re: Build failed in Jenkins: tapestry-trunk-freestyle #678

2012-01-30 Thread Ulrich Stärk
Weird. Both are set in ~/.gradle/gradle.properties. Could the change have caused this? On 30.01.2012 17:40, Apache Jenkins Server wrote: > See > > Changes: > > [hlship] Update the build to generate and upload PGP signatures alon

Re: Build failed in Jenkins: tapestry-trunk-freestyle #678

2012-01-30 Thread Ulrich Stärk
It did. See other email. On 30.01.2012 19:14, Ulrich Stärk wrote: > Weird. Both are set in ~/.gradle/gradle.properties. Could the change have > caused this? > > On 30.01.2012 17:40, Apache Jenkins Server wrote: >> See >> >> Chan

Re: svn commit: r1237745 - /tapestry/tapestry5/trunk/build.gradle

2012-01-30 Thread Ulrich Stärk
On 30.01.2012 17:01, hls...@apache.org wrote: > Author: hlship > Date: Mon Jan 30 16:01:47 2012 > New Revision: 1237745 > > URL: http://svn.apache.org/viewvc?rev=1237745&view=rev > Log: > Update the build to generate and upload PGP signatures along with the MD5 > checksums for the sources and java

Re: svn commit: r1237745 - /tapestry/tapestry5/trunk/build.gradle

2012-01-30 Thread Howard Lewis Ship
Apparently, I didn't understand snapshot deployment, I was only thinking in terms of manual execution of generateRelease; I'll figure out how to split doSign and canDeploy again. On Mon, Jan 30, 2012 at 10:23 AM, Ulrich Stärk wrote: > On 30.01.2012 17:01, hls...@apache.org wrote: >> Author: hlshi

Re: svn commit: r1237745 - /tapestry/tapestry5/trunk/build.gradle

2012-01-30 Thread Howard Lewis Ship
Latest couple of commits should fix it. On Mon, Jan 30, 2012 at 12:00 PM, Howard Lewis Ship wrote: > Apparently, I didn't understand snapshot deployment, I was only > thinking in terms of manual execution of generateRelease; I'll figure > out how to split doSign and canDeploy again. > > On Mon, J

buildbot success in ASF Buildbot on tapestry-trunk

2012-01-30 Thread buildbot
The Buildbot has finished a build on builder tapestry-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tapestry-trunk/builds/49 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: isis_ubuntu Build Reason: scheduler Build Source Stamp:

buildbot success in ASF Buildbot on tapestry-trunk

2012-01-30 Thread buildbot
The Buildbot has finished a build on builder tapestry-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tapestry-trunk/builds/50 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: isis_ubuntu Build Reason: scheduler Build Source Stamp:

Jenkins build is back to normal : tapestry-trunk-freestyle #679

2012-01-30 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org

Re: svn commit: r1237745 - /tapestry/tapestry5/trunk/build.gradle

2012-01-30 Thread Ulrich Stärk
Looks good, thanks! Uli Am 30.01.2012 um 22:18 schrieb Howard Lewis Ship : > Latest couple of commits should fix it. > > On Mon, Jan 30, 2012 at 12:00 PM, Howard Lewis Ship wrote: >> Apparently, I didn't understand snapshot deployment, I was only >> thinking in terms of manual execution of g