Re: [vote] release wicket 1.4.19
+1 code wise it runs fine for us. (was already on a snapshot with the latest stuff) On Wed, Oct 12, 2011 at 18:10, Igor Vaynberg igor.vaynb...@gmail.com wrote: This vote is to release wicket 1.4.19 Branch http://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.19 Artifacts http://people.apache.org/~ivaynberg/wicket-1.4.19/dist/ Maven repo https://repository.apache.org/content/repositories/orgapachewicket-057/ Changelog https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561version=12317570 This vote ends Saturday, October 15 at 9:00am (GMT-7) Please test the release and offer your vote. The Wicket team!
Re: [vote] release wicket 1.5.2
+1 to release Tested: - the application I work on - quickstart archetype - random wicket-examples - Maven3 build with JDK1.5 On Wed, Oct 12, 2011 at 8:23 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote: This vote is to release wicket 1.5.2 Branch http://svn.apache.org/repos/asf/wicket/branches/wicket-1.5.2 Artifacts http://people.apache.org/~ivaynberg/wicket-1.5.2/dist/ Maven repo https://repository.apache.org/content/repositories/orgapachewicket-060/ Changelog https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561version=12318078 This vote ends Saturday, October 15 at 10:00am (GMT-7) Please test the release and offer your vote. The Wicket team! -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
Re: [vote] release wicket 1.4.19
+1 Tested: - Maven3 build with JDK1.5 - random wicket-examples On Thu, Oct 13, 2011 at 10:47 AM, Johan Compagner jcompag...@gmail.com wrote: +1 code wise it runs fine for us. (was already on a snapshot with the latest stuff) On Wed, Oct 12, 2011 at 18:10, Igor Vaynberg igor.vaynb...@gmail.com wrote: This vote is to release wicket 1.4.19 Branch http://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.19 Artifacts http://people.apache.org/~ivaynberg/wicket-1.4.19/dist/ Maven repo https://repository.apache.org/content/repositories/orgapachewicket-057/ Changelog https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561version=12317570 This vote ends Saturday, October 15 at 9:00am (GMT-7) Please test the release and offer your vote. The Wicket team! -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
Re: [vote] release wicket 1.5.2
+1 to release This vote is to release wicket 1.5.2 Branch http://svn.apache.org/repos/asf/wicket/branches/wicket-1.5.2 Artifacts http://people.apache.org/~ivaynberg/wicket-1.5.2/dist/ Maven repo https://repository.apache.org/content/repositories/orgapachewicket-060/ Changelog https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561version=12318078 This vote ends Saturday, October 15 at 10:00am (GMT-7) Please test the release and offer your vote. The Wicket team!
Re: [vote] release wicket 1.5.2
+1 tested with a large application,looks promising -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/vote-release-wicket-1-5-2-tp3898844p3902138.html Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.
Re: [vote] release wicket 1.5.2
-1
WICKET-4116 fix broke a bunch of stuff
for example we no longer redirect from /page to /page?0 which causes problems
also querying request handlers for page instance no longer works. most
queries look like this:
if (pageHandler.isPageInstanceCreated())
return (Page)pageHandler.getPage();
public final boolean isPageInstanceCreated() {
return !pageComponentProvider.isNewPageInstance(); }
however, since isNewPageInstance() now caches the initial value of
'true' even though the page provider later did create the instance we
now erroneously assume the page instance was not created.
isNewPageInstance() is a horrible name, it really should be
isPageInstanceCreated(). if we need something like
wasPageInstanceProvided() - to know whether or not page provider was
created with or without a page instance to fix WICKET-4116 then we
should add it
or perhaps simpler names:
Page hasPageInstance() and boolean createdPageInstance()
-igor
On Wed, Oct 12, 2011 at 10:23 AM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
This vote is to release wicket 1.5.2
Branch
http://svn.apache.org/repos/asf/wicket/branches/wicket-1.5.2
Artifacts
http://people.apache.org/~ivaynberg/wicket-1.5.2/dist/
Maven repo
https://repository.apache.org/content/repositories/orgapachewicket-060/
Changelog
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561version=12318078
This vote ends Saturday, October 15 at 10:00am (GMT-7)
Please test the release and offer your vote.
The Wicket team!
Proposal: Moving wicketstuff.org Jenkins instance to a linux server (I volunteer to manage it)
Hello, Jenkins currently runs at wicketstuff.org/hudson. The wicketstuff.org server is running FreeBSD which is not directly supported by Jenkins and so upgrading and installing related tooling becomes a burden on the server admins. Recently there has been intermittent instability that causes jenkins to become unavailable and prevents developers from being easily able to generate and test new snapshot releases. My proposal is that we take advantage of the Jenkins community support for Linux that includes auto-installers and binary packages and switch to running the wicketstuff.org Jenkins instance on a Linux box. I am volunteering to host this on a VPS I have and to take care of the server side admin. If this is acceptable I would suggest moving jenkins from wicketstuff.org/hudson to a DNS A name like ci.wicketstuff.org that could point at my server. Then depending on the load I might ask to have the wicketstuff.org server setup as a slave to sometimes assist in building the projects but not be the main access point for the developers. Once this is setup I would also be interested in letting others contribute slaves to help with the build. In the past when I noticed that the wicketstuff.org/hudson server was down I would setup a private Jenkins instance to take care of building the SNAPSHOT's because I didn't want to run it in public with the same anyone can signup privileges. To get around this issue I have written a Jenkins authentication/authorization plugin that will restrict access to only members of a named github organization (i.e. only github users that are a member of the wicketstuff organization can access and invoke builds. This will let us manage access entirely through Github. The only restriction on the plugin right now is that the users affiliation in the team needs to be publicized. Plugin Link: https://wiki.jenkins-ci.org/display/JENKINS/Github+OAuth+Plugin I've published the 0.6 version of this plugin which now supports a post commit hook from github to trigger builds (i.e. no more @hourly polling is required). The test instance is here: http://rivulet.ca:8080/ Anyone with commit access in github that is a public member of the any team in the wicketstuff project can login and have the trigger build permission. Regards, Mike
Re: Proposal: Moving wicketstuff.org Jenkins instance to a linux server (I volunteer to manage it)
On Thu, Oct 13, 2011 at 11:53 PM, Michael O'Cleirigh michael.ocleir...@rivulet.ca wrote: Hello, Jenkins currently runs at wicketstuff.org/hudson. The wicketstuff.orgserver is running FreeBSD which is not directly supported by Jenkins and so upgrading and installing related tooling becomes a burden on the server admins. Recently there has been intermittent instability that causes jenkins to become unavailable and prevents developers from being easily able to generate and test new snapshot releases. My proposal is that we take advantage of the Jenkins community support for Linux that includes auto-installers and binary packages and switch to running the wicketstuff.org Jenkins instance on a Linux box. I am volunteering to host this on a VPS I have and to take care of the server side admin. If this is acceptable I would suggest moving jenkins from wicketstuff.org/hudson to a DNS A name like ci.wicketstuff.org that could point at my server. Then depending on the load I might ask to have the wicketstuff.org server setup as a slave to sometimes assist in building the projects but not be the main access point for the developers. Once this is setup I would also be interested in letting others contribute slaves to help with the build. In the past when I noticed that the wicketstuff.org/hudson server was down I would setup a private Jenkins instance to take care of building the SNAPSHOT's because I didn't want to run it in public with the same anyone can signup privileges. To get around this issue I have written a Jenkins authentication/authorization plugin that will restrict access to only members of a named github organization (i.e. only github users that are a member of the wicketstuff organization can access and invoke builds. This will let us manage access entirely through Github. The only restriction on the plugin right now is that the users affiliation in the team needs to be publicized. Plugin Link: https://wiki.jenkins-ci.org/**display/JENKINS/Github+OAuth+** Plugin https://wiki.jenkins-ci.org/display/JENKINS/Github+OAuth+Plugin I've published the 0.6 version of this plugin which now supports a post commit hook from github to trigger builds (i.e. no more @hourly polling is required). The test instance is here: http://rivulet.ca:8080/ Anyone with commit access in github that is a public member of the any team in the wicketstuff project can login and have the trigger build permission. Regards, Mike I'm +1000 for letting you handle all this build stuff and host it on your server. Copying Johan directly because IIRC the server it is currently on is his and I want to make sure he sees it. Big hooray! for Mike and all his endless work on wicketstuff!! -- Jeremy Thomerson http://wickettraining.com *Need a CMS for Wicket? Use Brix! http://brixcms.org*
Re: Proposal: Moving wicketstuff.org Jenkins instance to a linux server (I volunteer to manage it)
+1 to both Mike's proposal and Jeremy's reaction. -igor On Thu, Oct 13, 2011 at 9:08 PM, Jeremy Thomerson jer...@wickettraining.com wrote: On Thu, Oct 13, 2011 at 11:53 PM, Michael O'Cleirigh michael.ocleir...@rivulet.ca wrote: Hello, Jenkins currently runs at wicketstuff.org/hudson. The wicketstuff.orgserver is running FreeBSD which is not directly supported by Jenkins and so upgrading and installing related tooling becomes a burden on the server admins. Recently there has been intermittent instability that causes jenkins to become unavailable and prevents developers from being easily able to generate and test new snapshot releases. My proposal is that we take advantage of the Jenkins community support for Linux that includes auto-installers and binary packages and switch to running the wicketstuff.org Jenkins instance on a Linux box. I am volunteering to host this on a VPS I have and to take care of the server side admin. If this is acceptable I would suggest moving jenkins from wicketstuff.org/hudson to a DNS A name like ci.wicketstuff.org that could point at my server. Then depending on the load I might ask to have the wicketstuff.org server setup as a slave to sometimes assist in building the projects but not be the main access point for the developers. Once this is setup I would also be interested in letting others contribute slaves to help with the build. In the past when I noticed that the wicketstuff.org/hudson server was down I would setup a private Jenkins instance to take care of building the SNAPSHOT's because I didn't want to run it in public with the same anyone can signup privileges. To get around this issue I have written a Jenkins authentication/authorization plugin that will restrict access to only members of a named github organization (i.e. only github users that are a member of the wicketstuff organization can access and invoke builds. This will let us manage access entirely through Github. The only restriction on the plugin right now is that the users affiliation in the team needs to be publicized. Plugin Link: https://wiki.jenkins-ci.org/**display/JENKINS/Github+OAuth+** Plugin https://wiki.jenkins-ci.org/display/JENKINS/Github+OAuth+Plugin I've published the 0.6 version of this plugin which now supports a post commit hook from github to trigger builds (i.e. no more @hourly polling is required). The test instance is here: http://rivulet.ca:8080/ Anyone with commit access in github that is a public member of the any team in the wicketstuff project can login and have the trigger build permission. Regards, Mike I'm +1000 for letting you handle all this build stuff and host it on your server. Copying Johan directly because IIRC the server it is currently on is his and I want to make sure he sees it. Big hooray! for Mike and all his endless work on wicketstuff!! -- Jeremy Thomerson http://wickettraining.com *Need a CMS for Wicket? Use Brix! http://brixcms.org*
