Re: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
Hi, Recently in my company we moved from TeamCity to Hudson for two major reasons: - Hudson can start several runners (i.e. build several projects at once) while TC agent can build at most one project at a time - Hudson knows Maven, i.e. after building project X it builds all projects that depend on X We even contributed a tool to Hudson that migrates TC configuration to Hudson one, but I understand you already did that part. So I'm +1 for the change, but I don't have permissions to the box where wicketstuff.org is running. 2010/7/21 Michael O'Cleirigh > Hello, > > I've been using Hudson reliably to build wicketstuff core snapshot's and > deploying them into the sonatype maven repository. I put together an older > machine for this purpose (P4 1.8Ghz) and while it worked at first recently > there have been memory issues (at least one of the DDR1 DIMM's is bad and > the JVM keeps crashing). I have the builds running temporarily somewhere > else but the long term solution is to run Hudson on a box that can be opened > up to the other wicketstuff developers. > > My proposal is to replace TeamCity on wicketstuff.org with Hudson and then > do the necessary setup to allow wicketstuff developers access to it for > initiating builds and viewing the projects status. > > I am willing to do all of the necessary setup and configuration to make > this happen; basically copying over what I have working right now plus > adding in user authentication. > > The easiest way would be if I could get a user account on the > wicketstuff.org server (at least initially) and then get everything setup. > > There are still some questions around if the wicketstuff.org box is still > banned by sourceforge but I think the best way to find out the answer is to > try and see what happens. > > Regards, > > Mike > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
There are some developments unfolding in the near future that might help out on the future of our wicketstuff server and/or its infrastructure. I don't have the full details to those plans yet, and don't know if they entail a build server of some sorts. I'm perfectly happy with switching to hudson—we use it at work and it has been a godsend compared to the other available solutions (though I still don't like the UI). I hope we can wait a (couple of) week(s) and see the future plans unfold to see what the details are, especially with respect to a build server. I'll ask around to see if it is part of that deal. Martijn On Wed, Jul 21, 2010 at 4:06 AM, Michael O'Cleirigh wrote: > Hello, > > I've been using Hudson reliably to build wicketstuff core snapshot's and > deploying them into the sonatype maven repository. I put together an older > machine for this purpose (P4 1.8Ghz) and while it worked at first recently > there have been memory issues (at least one of the DDR1 DIMM's is bad and > the JVM keeps crashing). I have the builds running temporarily somewhere > else but the long term solution is to run Hudson on a box that can be opened > up to the other wicketstuff developers. > > My proposal is to replace TeamCity on wicketstuff.org with Hudson and then > do the necessary setup to allow wicketstuff developers access to it for > initiating builds and viewing the projects status. > > I am willing to do all of the necessary setup and configuration to make this > happen; basically copying over what I have working right now plus adding in > user authentication. > > The easiest way would be if I could get a user account on the > wicketstuff.org server (at least initially) and then get everything setup. > > There are still some questions around if the wicketstuff.org box is still > banned by sourceforge but I think the best way to find out the answer is to > try and see what happens. > > Regards, > > Mike > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8
RE: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
Hi, If anyone is looking for a Wicket contract position in Edinburgh please get in contact. Best regards, Steven Steven Tierney Bright Purple Resourcing Ltd Senior Consultant The Eagle Building, 19 Rose Street, Edinburgh, EH2 2PR Office: +44 131 473 7045 (Direct Line) +44 131 473 7030 Fax: +44 131 473 7040 Website: www.brightpurple.co.uk Twitter: twitter.com/BrightPurpleR Bright Purple Resourcing - "PERFECTLY PLACING PROFESSIONALS SINCE 1995" Think before you print. Please do not print this email unless you really need to.-Original Message- From: Michael O'Cleirigh [mailto:michael.ocleir...@rivulet.ca] Sent: 21 July 2010 03:07 To: dev@wicket.apache.org Subject: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects Hello, I've been using Hudson reliably to build wicketstuff core snapshot's and deploying them into the sonatype maven repository. I put together an older machine for this purpose (P4 1.8Ghz) and while it worked at first recently there have been memory issues (at least one of the DDR1 DIMM's is bad and the JVM keeps crashing). I have the builds running temporarily somewhere else but the long term solution is to run Hudson on a box that can be opened up to the other wicketstuff developers. My proposal is to replace TeamCity on wicketstuff.org with Hudson and then do the necessary setup to allow wicketstuff developers access to it for initiating builds and viewing the projects status. I am willing to do all of the necessary setup and configuration to make this happen; basically copying over what I have working right now plus adding in user authentication. The easiest way would be if I could get a user account on the wicketstuff.org server (at least initially) and then get everything setup. There are still some questions around if the wicketstuff.org box is still banned by sourceforge but I think the best way to find out the answer is to try and see what happens. Regards, Mike Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Employees of Bright Purple Resourcing are expressly required not to make defamatory statements and not to infringe or authorise any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy and outside the scope of the employment of the individual concerned. The company will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. Bright Purple Resourcing is a company registered in Scotland with company number SC155147. VAT Number 658 2716 10. Registered office address: Eagle Building, 19 Rose Street, Edinburgh. EH2 2PR www.brightpurple.co.uk
Re: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
My little bird told me that no build server is part of the new deal which is slated to be announced mid-august, so IMO we should not delay the migration off of teamcity and setup hudson. I'll contact the sysadmin for the box to see if I can grant direct access, or that only "trusted" folks are allowed. Martijn On Wed, Jul 21, 2010 at 9:43 AM, Martijn Dashorst wrote: > There are some developments unfolding in the near future that might > help out on the future of our wicketstuff server and/or its > infrastructure. I don't have the full details to those plans yet, and > don't know if they entail a build server of some sorts. > > I'm perfectly happy with switching to hudson—we use it at work and it > has been a godsend compared to the other available solutions (though I > still don't like the UI). > > I hope we can wait a (couple of) week(s) and see the future plans > unfold to see what the details are, especially with respect to a build > server. I'll ask around to see if it is part of that deal. > > Martijn > > On Wed, Jul 21, 2010 at 4:06 AM, Michael O'Cleirigh > wrote: >> Hello, >> >> I've been using Hudson reliably to build wicketstuff core snapshot's and >> deploying them into the sonatype maven repository. I put together an older >> machine for this purpose (P4 1.8Ghz) and while it worked at first recently >> there have been memory issues (at least one of the DDR1 DIMM's is bad and >> the JVM keeps crashing). I have the builds running temporarily somewhere >> else but the long term solution is to run Hudson on a box that can be opened >> up to the other wicketstuff developers. >> >> My proposal is to replace TeamCity on wicketstuff.org with Hudson and then >> do the necessary setup to allow wicketstuff developers access to it for >> initiating builds and viewing the projects status. >> >> I am willing to do all of the necessary setup and configuration to make this >> happen; basically copying over what I have working right now plus adding in >> user authentication. >> >> The easiest way would be if I could get a user account on the >> wicketstuff.org server (at least initially) and then get everything setup. >> >> There are still some questions around if the wicketstuff.org box is still >> banned by sourceforge but I think the best way to find out the answer is to >> try and see what happens. >> >> Regards, >> >> Mike >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8
Re: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
- Hudson can start several runners (i.e. build several projects at once) while TC agent can build at most one project at a time Just to keep the facts straight: at my company we have several TC agents on one machine. Works without problems. Regards, Erik. Op 21-07-10 09:31, Martin Grigorov wrote: Hi, Recently in my company we moved from TeamCity to Hudson for two major reasons: - Hudson knows Maven, i.e. after building project X it builds all projects that depend on X We even contributed a tool to Hudson that migrates TC configuration to Hudson one, but I understand you already did that part. So I'm +1 for the change, but I don't have permissions to the box where wicketstuff.org is running. -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/
Re: Jekyll generated website going live soon...
Hi, Few feedbacks: * two link on the page is 404-ing: http://wicket.apache.org/contribute/writing-documentation.html and http://wicket.apache.org/contribute/building-from-svn.html * also for some reason I couldn't find the page about mailing lists and archives (they were under the big Community link on the old page), where are they now? The new site is really nice btw ;) Regards, Peter 2010-07-21 01:20 keltezéssel, Martijn Dashorst írta: > The new site is now live, and updating is instantaneous. Many thanks > go to Joe Shaefer of Apache infra for helping me out enabling this. > > Things worthy of note: > > - javadocs live in > https://svn.apache.org/repos/asf/wicket/common/site/apidocs > - I uploaded only the latest and greatest API docs, no more 1.4.3, > 1.4.4, 1.4.5, 1.4.6 etc, just 1.4 javadocs (which contains whatever > the latest release for 1.4 was) > > Martijn > > On Wed, Jul 21, 2010 at 12:21 AM, Martijn Dashorst > wrote: >> I'm working with the infra@ to get our new website (based on the old >> style) live using svnpubsub. >> >> When you cut a release, the easiest thing to add it to our new website >> is to check it out: >> >> svn co https://svn.apache.org/repos/asf/wicket/common/site/trunk wicket-site >> >> cd wicket-site >> >> and edit the _config.yaml file. The contents are currently: >> >> destination: ./_site >> auto:false >> lsi: false >> server_port: 4000 >> pygments:true >> markdown:maruku >> permalink: date >> maruku: >> use_tex:false >> use_divs: false >> png_dir:images/latex >> png_url:/images/latex >> exclude:readme.md >> wicket: >>version:1.4.9 >>released: 2010-05-24 >>versions: [1.3.7, 1.3-SNAPSHOT, 1.4.7, 1.4.8, 1.4.9, >> 1.4-SNAPSHOT, 1.5-SNAPSHOT] >> >> >> You'll need to edit the wicket part: modify the version, update the >> released date, and add the new version to the versions list. >> >> Run jekyll: >> >> jekyll --auto --server >> >> This will generate the site and update all relevant pages, including >> the menu structure, the quickstart and the doap.rdf file >> >> See if the site works by opening a browser and going to http://localhost:4000 >> >> Add a post with the release notes in _posts >> >> Ensure the post is visible on the front page. >> >> Now all you need to do is svn commit the changes... >> >> Martijn
Re: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
hudson is just a war right? so that can be dumped by anybody of the wicket devs to onto the tomcat webapp dir. What more does hudson need? On Wed, Jul 21, 2010 at 11:14, Martijn Dashorst wrote: > My little bird told me that no build server is part of the new deal > which is slated to be announced mid-august, so IMO we should not delay > the migration off of teamcity and setup hudson. I'll contact the > sysadmin for the box to see if I can grant direct access, or that only > "trusted" folks are allowed. > > Martijn > > On Wed, Jul 21, 2010 at 9:43 AM, Martijn Dashorst > wrote: >> There are some developments unfolding in the near future that might >> help out on the future of our wicketstuff server and/or its >> infrastructure. I don't have the full details to those plans yet, and >> don't know if they entail a build server of some sorts. >> >> I'm perfectly happy with switching to hudson—we use it at work and it >> has been a godsend compared to the other available solutions (though I >> still don't like the UI). >> >> I hope we can wait a (couple of) week(s) and see the future plans >> unfold to see what the details are, especially with respect to a build >> server. I'll ask around to see if it is part of that deal. >> >> Martijn >> >> On Wed, Jul 21, 2010 at 4:06 AM, Michael O'Cleirigh >> wrote: >>> Hello, >>> >>> I've been using Hudson reliably to build wicketstuff core snapshot's and >>> deploying them into the sonatype maven repository. I put together an older >>> machine for this purpose (P4 1.8Ghz) and while it worked at first recently >>> there have been memory issues (at least one of the DDR1 DIMM's is bad and >>> the JVM keeps crashing). I have the builds running temporarily somewhere >>> else but the long term solution is to run Hudson on a box that can be opened >>> up to the other wicketstuff developers. >>> >>> My proposal is to replace TeamCity on wicketstuff.org with Hudson and then >>> do the necessary setup to allow wicketstuff developers access to it for >>> initiating builds and viewing the projects status. >>> >>> I am willing to do all of the necessary setup and configuration to make this >>> happen; basically copying over what I have working right now plus adding in >>> user authentication. >>> >>> The easiest way would be if I could get a user account on the >>> wicketstuff.org server (at least initially) and then get everything setup. >>> >>> There are still some questions around if the wicketstuff.org box is still >>> banned by sourceforge but I think the best way to find out the answer is to >>> try and see what happens. >>> >>> Regards, >>> >>> Mike >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.4 increases type safety for web applications >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >
Re: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
Security needs to be enabled and other stuff. Deploying as a war does have some drawbacks: restarting using the UI won't work, installing/updating plugins/new versions of hudson is enabled by default. Martijn On Wed, Jul 21, 2010 at 2:46 PM, Johan Compagner wrote: > hudson is just a war right? > so that can be dumped by anybody of the wicket devs to onto the tomcat > webapp dir. > > What more does hudson need? > > > On Wed, Jul 21, 2010 at 11:14, Martijn Dashorst > wrote: >> My little bird told me that no build server is part of the new deal >> which is slated to be announced mid-august, so IMO we should not delay >> the migration off of teamcity and setup hudson. I'll contact the >> sysadmin for the box to see if I can grant direct access, or that only >> "trusted" folks are allowed. >> >> Martijn >> >> On Wed, Jul 21, 2010 at 9:43 AM, Martijn Dashorst >> wrote: >>> There are some developments unfolding in the near future that might >>> help out on the future of our wicketstuff server and/or its >>> infrastructure. I don't have the full details to those plans yet, and >>> don't know if they entail a build server of some sorts. >>> >>> I'm perfectly happy with switching to hudson—we use it at work and it >>> has been a godsend compared to the other available solutions (though I >>> still don't like the UI). >>> >>> I hope we can wait a (couple of) week(s) and see the future plans >>> unfold to see what the details are, especially with respect to a build >>> server. I'll ask around to see if it is part of that deal. >>> >>> Martijn >>> >>> On Wed, Jul 21, 2010 at 4:06 AM, Michael O'Cleirigh >>> wrote: Hello, I've been using Hudson reliably to build wicketstuff core snapshot's and deploying them into the sonatype maven repository. I put together an older machine for this purpose (P4 1.8Ghz) and while it worked at first recently there have been memory issues (at least one of the DDR1 DIMM's is bad and the JVM keeps crashing). I have the builds running temporarily somewhere else but the long term solution is to run Hudson on a box that can be opened up to the other wicketstuff developers. My proposal is to replace TeamCity on wicketstuff.org with Hudson and then do the necessary setup to allow wicketstuff developers access to it for initiating builds and viewing the projects status. I am willing to do all of the necessary setup and configuration to make this happen; basically copying over what I have working right now plus adding in user authentication. The easiest way would be if I could get a user account on the wicketstuff.org server (at least initially) and then get everything setup. There are still some questions around if the wicketstuff.org box is still banned by sourceforge but I think the best way to find out the answer is to try and see what happens. Regards, Mike >>> >>> >>> >>> -- >>> Become a Wicket expert, learn from the best: http://wicketinaction.com >>> Apache Wicket 1.4 increases type safety for web applications >>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >>> >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.4 increases type safety for web applications >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >> > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8
Re: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
This will give you a rough idea of what you need for Hudson. It does need some disk space: http://wiki.hudson-ci.org/display/HUDSON/Administering+Hudson On Wed, Jul 21, 2010 at 8:51 AM, Martijn Dashorst wrote: > Security needs to be enabled and other stuff. Deploying as a war does > have some drawbacks: restarting using the UI won't work, > installing/updating plugins/new versions of hudson is enabled by > default. > > Martijn > > On Wed, Jul 21, 2010 at 2:46 PM, Johan Compagner wrote: >> hudson is just a war right? >> so that can be dumped by anybody of the wicket devs to onto the tomcat >> webapp dir. >> >> What more does hudson need? >> >> >> On Wed, Jul 21, 2010 at 11:14, Martijn Dashorst >> wrote: >>> My little bird told me that no build server is part of the new deal >>> which is slated to be announced mid-august, so IMO we should not delay >>> the migration off of teamcity and setup hudson. I'll contact the >>> sysadmin for the box to see if I can grant direct access, or that only >>> "trusted" folks are allowed. >>> >>> Martijn >>> >>> On Wed, Jul 21, 2010 at 9:43 AM, Martijn Dashorst >>> wrote: There are some developments unfolding in the near future that might help out on the future of our wicketstuff server and/or its infrastructure. I don't have the full details to those plans yet, and don't know if they entail a build server of some sorts. I'm perfectly happy with switching to hudson—we use it at work and it has been a godsend compared to the other available solutions (though I still don't like the UI). I hope we can wait a (couple of) week(s) and see the future plans unfold to see what the details are, especially with respect to a build server. I'll ask around to see if it is part of that deal. Martijn On Wed, Jul 21, 2010 at 4:06 AM, Michael O'Cleirigh wrote: > Hello, > > I've been using Hudson reliably to build wicketstuff core snapshot's and > deploying them into the sonatype maven repository. I put together an > older > machine for this purpose (P4 1.8Ghz) and while it worked at first recently > there have been memory issues (at least one of the DDR1 DIMM's is bad and > the JVM keeps crashing). I have the builds running temporarily somewhere > else but the long term solution is to run Hudson on a box that can be > opened > up to the other wicketstuff developers. > > My proposal is to replace TeamCity on wicketstuff.org with Hudson and then > do the necessary setup to allow wicketstuff developers access to it for > initiating builds and viewing the projects status. > > I am willing to do all of the necessary setup and configuration to make > this > happen; basically copying over what I have working right now plus adding > in > user authentication. > > The easiest way would be if I could get a user account on the > wicketstuff.org server (at least initially) and then get everything setup. > > There are still some questions around if the wicketstuff.org box is still > banned by sourceforge but I think the best way to find out the answer is > to > try and see what happens. > > Regards, > > Mike > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >>> >>> >>> >>> -- >>> Become a Wicket expert, learn from the best: http://wicketinaction.com >>> Apache Wicket 1.4 increases type safety for web applications >>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >>> >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >
Re: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
how do you deploy then? has hudson its container (tomcat)?? Then we also need another port. And have all kind of apache config to support things like: wicketstuff.org/hudson hmm that i dont like. It should just run on the tomcat instance we have. On Wed, Jul 21, 2010 at 14:51, Martijn Dashorst wrote: > Security needs to be enabled and other stuff. Deploying as a war does > have some drawbacks: restarting using the UI won't work, > installing/updating plugins/new versions of hudson is enabled by > default. > > Martijn > > On Wed, Jul 21, 2010 at 2:46 PM, Johan Compagner wrote: >> hudson is just a war right? >> so that can be dumped by anybody of the wicket devs to onto the tomcat >> webapp dir. >> >> What more does hudson need? >> >> >> On Wed, Jul 21, 2010 at 11:14, Martijn Dashorst >> wrote: >>> My little bird told me that no build server is part of the new deal >>> which is slated to be announced mid-august, so IMO we should not delay >>> the migration off of teamcity and setup hudson. I'll contact the >>> sysadmin for the box to see if I can grant direct access, or that only >>> "trusted" folks are allowed. >>> >>> Martijn >>> >>> On Wed, Jul 21, 2010 at 9:43 AM, Martijn Dashorst >>> wrote: There are some developments unfolding in the near future that might help out on the future of our wicketstuff server and/or its infrastructure. I don't have the full details to those plans yet, and don't know if they entail a build server of some sorts. I'm perfectly happy with switching to hudson—we use it at work and it has been a godsend compared to the other available solutions (though I still don't like the UI). I hope we can wait a (couple of) week(s) and see the future plans unfold to see what the details are, especially with respect to a build server. I'll ask around to see if it is part of that deal. Martijn On Wed, Jul 21, 2010 at 4:06 AM, Michael O'Cleirigh wrote: > Hello, > > I've been using Hudson reliably to build wicketstuff core snapshot's and > deploying them into the sonatype maven repository. I put together an > older > machine for this purpose (P4 1.8Ghz) and while it worked at first recently > there have been memory issues (at least one of the DDR1 DIMM's is bad and > the JVM keeps crashing). I have the builds running temporarily somewhere > else but the long term solution is to run Hudson on a box that can be > opened > up to the other wicketstuff developers. > > My proposal is to replace TeamCity on wicketstuff.org with Hudson and then > do the necessary setup to allow wicketstuff developers access to it for > initiating builds and viewing the projects status. > > I am willing to do all of the necessary setup and configuration to make > this > happen; basically copying over what I have working right now plus adding > in > user authentication. > > The easiest way would be if I could get a user account on the > wicketstuff.org server (at least initially) and then get everything setup. > > There are still some questions around if the wicketstuff.org box is still > banned by sourceforge but I think the best way to find out the answer is > to > try and see what happens. > > Regards, > > Mike > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >>> >>> >>> >>> -- >>> Become a Wicket expert, learn from the best: http://wicketinaction.com >>> Apache Wicket 1.4 increases type safety for web applications >>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >>> >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >
Re: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
Here are the instructions for setting it up on linux/unix: http://wiki.hudson-ci.org/display/HUDSON/Installing+Hudson#InstallingHudson-Unix%2FLinuxInstallation You *can* just do: java -jar hudson.war and it'll run. That's just a quick way to get it up and running to play around with it. On Wed, Jul 21, 2010 at 9:11 AM, Johan Compagner wrote: > how do you deploy then? > has hudson its container (tomcat)?? > Then we also need another port. And have all kind of apache config to > support things like: > > wicketstuff.org/hudson > > hmm that i dont like. It should just run on the tomcat instance we have. > > > On Wed, Jul 21, 2010 at 14:51, Martijn Dashorst > wrote: >> Security needs to be enabled and other stuff. Deploying as a war does >> have some drawbacks: restarting using the UI won't work, >> installing/updating plugins/new versions of hudson is enabled by >> default. >> >> Martijn >> >> On Wed, Jul 21, 2010 at 2:46 PM, Johan Compagner >> wrote: >>> hudson is just a war right? >>> so that can be dumped by anybody of the wicket devs to onto the tomcat >>> webapp dir. >>> >>> What more does hudson need? >>> >>> >>> On Wed, Jul 21, 2010 at 11:14, Martijn Dashorst >>> wrote: My little bird told me that no build server is part of the new deal which is slated to be announced mid-august, so IMO we should not delay the migration off of teamcity and setup hudson. I'll contact the sysadmin for the box to see if I can grant direct access, or that only "trusted" folks are allowed. Martijn On Wed, Jul 21, 2010 at 9:43 AM, Martijn Dashorst wrote: > There are some developments unfolding in the near future that might > help out on the future of our wicketstuff server and/or its > infrastructure. I don't have the full details to those plans yet, and > don't know if they entail a build server of some sorts. > > I'm perfectly happy with switching to hudson—we use it at work and it > has been a godsend compared to the other available solutions (though I > still don't like the UI). > > I hope we can wait a (couple of) week(s) and see the future plans > unfold to see what the details are, especially with respect to a build > server. I'll ask around to see if it is part of that deal. > > Martijn > > On Wed, Jul 21, 2010 at 4:06 AM, Michael O'Cleirigh > wrote: >> Hello, >> >> I've been using Hudson reliably to build wicketstuff core snapshot's and >> deploying them into the sonatype maven repository. I put together an >> older >> machine for this purpose (P4 1.8Ghz) and while it worked at first >> recently >> there have been memory issues (at least one of the DDR1 DIMM's is bad and >> the JVM keeps crashing). I have the builds running temporarily >> somewhere >> else but the long term solution is to run Hudson on a box that can be >> opened >> up to the other wicketstuff developers. >> >> My proposal is to replace TeamCity on wicketstuff.org with Hudson and >> then >> do the necessary setup to allow wicketstuff developers access to it for >> initiating builds and viewing the projects status. >> >> I am willing to do all of the necessary setup and configuration to make >> this >> happen; basically copying over what I have working right now plus adding >> in >> user authentication. >> >> The easiest way would be if I could get a user account on the >> wicketstuff.org server (at least initially) and then get everything >> setup. >> >> There are still some questions around if the wicketstuff.org box is still >> banned by sourceforge but I think the best way to find out the answer is >> to >> try and see what happens. >> >> Regards, >> >> Mike >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >>> >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.4 increases type safety for web applications >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >> >
Re: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
its a FreeBSD server, so dont know if that is all the same that a linux one. But still everywhere i see java -jar hudson.war or hudson start That means that hudson has its own web container right? Where does that run on? which port? Then again also changes to apache must be done to map http://wicketstuff.org/hudson to localhost:HUDSONPORT/ so i rather have it just running inside the webcontainer we already have. On Wed, Jul 21, 2010 at 15:28, James Carman wrote: > Here are the instructions for setting it up on linux/unix: > > http://wiki.hudson-ci.org/display/HUDSON/Installing+Hudson#InstallingHudson-Unix%2FLinuxInstallation > > You *can* just do: > > java -jar hudson.war > > and it'll run. That's just a quick way to get it up and running to > play around with it. > > On Wed, Jul 21, 2010 at 9:11 AM, Johan Compagner wrote: >> how do you deploy then? >> has hudson its container (tomcat)?? >> Then we also need another port. And have all kind of apache config to >> support things like: >> >> wicketstuff.org/hudson >> >> hmm that i dont like. It should just run on the tomcat instance we have. >> >> >> On Wed, Jul 21, 2010 at 14:51, Martijn Dashorst >> wrote: >>> Security needs to be enabled and other stuff. Deploying as a war does >>> have some drawbacks: restarting using the UI won't work, >>> installing/updating plugins/new versions of hudson is enabled by >>> default. >>> >>> Martijn >>> >>> On Wed, Jul 21, 2010 at 2:46 PM, Johan Compagner >>> wrote: hudson is just a war right? so that can be dumped by anybody of the wicket devs to onto the tomcat webapp dir. What more does hudson need? On Wed, Jul 21, 2010 at 11:14, Martijn Dashorst wrote: > My little bird told me that no build server is part of the new deal > which is slated to be announced mid-august, so IMO we should not delay > the migration off of teamcity and setup hudson. I'll contact the > sysadmin for the box to see if I can grant direct access, or that only > "trusted" folks are allowed. > > Martijn > > On Wed, Jul 21, 2010 at 9:43 AM, Martijn Dashorst > wrote: >> There are some developments unfolding in the near future that might >> help out on the future of our wicketstuff server and/or its >> infrastructure. I don't have the full details to those plans yet, and >> don't know if they entail a build server of some sorts. >> >> I'm perfectly happy with switching to hudson—we use it at work and it >> has been a godsend compared to the other available solutions (though I >> still don't like the UI). >> >> I hope we can wait a (couple of) week(s) and see the future plans >> unfold to see what the details are, especially with respect to a build >> server. I'll ask around to see if it is part of that deal. >> >> Martijn >> >> On Wed, Jul 21, 2010 at 4:06 AM, Michael O'Cleirigh >> wrote: >>> Hello, >>> >>> I've been using Hudson reliably to build wicketstuff core snapshot's and >>> deploying them into the sonatype maven repository. I put together an >>> older >>> machine for this purpose (P4 1.8Ghz) and while it worked at first >>> recently >>> there have been memory issues (at least one of the DDR1 DIMM's is bad >>> and >>> the JVM keeps crashing). I have the builds running temporarily >>> somewhere >>> else but the long term solution is to run Hudson on a box that can be >>> opened >>> up to the other wicketstuff developers. >>> >>> My proposal is to replace TeamCity on wicketstuff.org with Hudson and >>> then >>> do the necessary setup to allow wicketstuff developers access to it for >>> initiating builds and viewing the projects status. >>> >>> I am willing to do all of the necessary setup and configuration to make >>> this >>> happen; basically copying over what I have working right now plus >>> adding in >>> user authentication. >>> >>> The easiest way would be if I could get a user account on the >>> wicketstuff.org server (at least initially) and then get everything >>> setup. >>> >>> There are still some questions around if the wicketstuff.org box is >>> still >>> banned by sourceforge but I think the best way to find out the answer >>> is to >>> try and see what happens. >>> >>> Regards, >>> >>> Mike >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.4 increases type safety for web applications >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >> > > > > -- > Become a Wicket exp
Re: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
which is possible, but we should ensure that pranksters won't be shutting down our server... Martijn On Wed, Jul 21, 2010 at 3:58 PM, Johan Compagner wrote: > its a FreeBSD server, so dont know if that is all the same that a linux one. > > But still everywhere i see java -jar hudson.war or hudson start > > That means that hudson has its own web container right? Where does > that run on? which port? > Then again also changes to apache must be done to map > http://wicketstuff.org/hudson to localhost:HUDSONPORT/ > > so i rather have it just running inside the webcontainer we already have. > > > On Wed, Jul 21, 2010 at 15:28, James Carman > wrote: >> Here are the instructions for setting it up on linux/unix: >> >> http://wiki.hudson-ci.org/display/HUDSON/Installing+Hudson#InstallingHudson-Unix%2FLinuxInstallation >> >> You *can* just do: >> >> java -jar hudson.war >> >> and it'll run. That's just a quick way to get it up and running to >> play around with it. >> >> On Wed, Jul 21, 2010 at 9:11 AM, Johan Compagner >> wrote: >>> how do you deploy then? >>> has hudson its container (tomcat)?? >>> Then we also need another port. And have all kind of apache config to >>> support things like: >>> >>> wicketstuff.org/hudson >>> >>> hmm that i dont like. It should just run on the tomcat instance we have. >>> >>> >>> On Wed, Jul 21, 2010 at 14:51, Martijn Dashorst >>> wrote: Security needs to be enabled and other stuff. Deploying as a war does have some drawbacks: restarting using the UI won't work, installing/updating plugins/new versions of hudson is enabled by default. Martijn On Wed, Jul 21, 2010 at 2:46 PM, Johan Compagner wrote: > hudson is just a war right? > so that can be dumped by anybody of the wicket devs to onto the tomcat > webapp dir. > > What more does hudson need? > > > On Wed, Jul 21, 2010 at 11:14, Martijn Dashorst > wrote: >> My little bird told me that no build server is part of the new deal >> which is slated to be announced mid-august, so IMO we should not delay >> the migration off of teamcity and setup hudson. I'll contact the >> sysadmin for the box to see if I can grant direct access, or that only >> "trusted" folks are allowed. >> >> Martijn >> >> On Wed, Jul 21, 2010 at 9:43 AM, Martijn Dashorst >> wrote: >>> There are some developments unfolding in the near future that might >>> help out on the future of our wicketstuff server and/or its >>> infrastructure. I don't have the full details to those plans yet, and >>> don't know if they entail a build server of some sorts. >>> >>> I'm perfectly happy with switching to hudson—we use it at work and it >>> has been a godsend compared to the other available solutions (though I >>> still don't like the UI). >>> >>> I hope we can wait a (couple of) week(s) and see the future plans >>> unfold to see what the details are, especially with respect to a build >>> server. I'll ask around to see if it is part of that deal. >>> >>> Martijn >>> >>> On Wed, Jul 21, 2010 at 4:06 AM, Michael O'Cleirigh >>> wrote: Hello, I've been using Hudson reliably to build wicketstuff core snapshot's and deploying them into the sonatype maven repository. I put together an older machine for this purpose (P4 1.8Ghz) and while it worked at first recently there have been memory issues (at least one of the DDR1 DIMM's is bad and the JVM keeps crashing). I have the builds running temporarily somewhere else but the long term solution is to run Hudson on a box that can be opened up to the other wicketstuff developers. My proposal is to replace TeamCity on wicketstuff.org with Hudson and then do the necessary setup to allow wicketstuff developers access to it for initiating builds and viewing the projects status. I am willing to do all of the necessary setup and configuration to make this happen; basically copying over what I have working right now plus adding in user authentication. The easiest way would be if I could get a user account on the wicketstuff.org server (at least initially) and then get everything setup. There are still some questions around if the wicketstuff.org box is still banned by sourceforge but I think the best way to find out the answer is to try and see what happens. Regards, Mike
Re: [proposal] Replace TeamCity on wicketstuff.org with Hudson for building wicketstuff projects
In linux I've been using the screen command like this: screen java -jar hudson.war --httpPort=9090 Then detaching and letting it run. Running it like this is useful if auto update doesn't work and a manual restart is required. Google seems to show that the 'screen' command also exists for FreeBSD which would make this setup easy. The big space use when using maven is that all the dependencies are downloaded into ~/.m2/repository of the user running maven. Also when the maven deploy goal is run all of the artifacts will be installed into the local repository aswell. My wicketstuff core hudson jobs don't archive artifacts in hudson (this lets the build history be longer) but periodically the ~/.m2/repository directory needs to be cleared out to reclaim space and manual access is useful for this. The oss.sonatype.org CI username/password need to be placed into the ~/.m2/settings.xml for the user running hudson. By default hudson runs on port 8080 but using the --httpPort option it can be run on any port. Probably there is a way to set the host aswell so that it could be forced onto 127.0.0.1 and then the apache interface would be the only way to access it. In terms of access control there is the option to require users to specify a username/password and then assign appropriate rights to each user. I think the power to create users can also be delegated. This would prevent anyone from shutting down the server unless they had the access to do it. I checked and Hudson when run this way uses the: Winstone Servlet Engine v0.9.10 The actual hudson configuration and job configuration files are located by default in the ~/.hudson directory I would be able to create a starting point for this directory with the suitable access controls enabled and provide it with the installation steps to the person with wicketstuff.org server access. That way it could be deployed in a secure way without risk of tampering before it is setup properly. Regards, Mike Here are the instructions for setting it up on linux/unix: http://wiki.hudson-ci.org/display/HUDSON/Installing+Hudson#InstallingHudson-Unix%2FLinuxInstallation You *can* just do: java -jar hudson.war and it'll run. That's just a quick way to get it up and running to play around with it. On Wed, Jul 21, 2010 at 9:11 AM, Johan Compagner wrote: how do you deploy then? has hudson its container (tomcat)?? Then we also need another port. And have all kind of apache config to support things like: wicketstuff.org/hudson hmm that i dont like. It should just run on the tomcat instance we have. On Wed, Jul 21, 2010 at 14:51, Martijn Dashorst wrote: Security needs to be enabled and other stuff. Deploying as a war does have some drawbacks: restarting using the UI won't work, installing/updating plugins/new versions of hudson is enabled by default. Martijn On Wed, Jul 21, 2010 at 2:46 PM, Johan Compagner wrote: hudson is just a war right? so that can be dumped by anybody of the wicket devs to onto the tomcat webapp dir. What more does hudson need? On Wed, Jul 21, 2010 at 11:14, Martijn Dashorst wrote: My little bird told me that no build server is part of the new deal which is slated to be announced mid-august, so IMO we should not delay the migration off of teamcity and setup hudson. I'll contact the sysadmin for the box to see if I can grant direct access, or that only "trusted" folks are allowed. Martijn On Wed, Jul 21, 2010 at 9:43 AM, Martijn Dashorst wrote: There are some developments unfolding in the near future that might help out on the future of our wicketstuff server and/or its infrastructure. I don't have the full details to those plans yet, and don't know if they entail a build server of some sorts. I'm perfectly happy with switching to hudson—we use it at work and it has been a godsend compared to the other available solutions (though I still don't like the UI). I hope we can wait a (couple of) week(s) and see the future plans unfold to see what the details are, especially with respect to a build server. I'll ask around to see if it is part of that deal. Martijn On Wed, Jul 21, 2010 at 4:06 AM, Michael O'Cleirigh wrote: Hello, I've been using Hudson reliably to build wicketstuff core snapshot's and deploying them into the sonatype maven repository. I put together an older machine for this purpose (P4 1.8Ghz) and while it worked at first recently there have been memory issues (at least one of the DDR1 DIMM's is bad and the JVM keeps crashing). I have the builds running temporarily somewhere else but the long term solution is to run Hudson on a box that can be opened up to the other wicketstuff developers. My proposal is to replace TeamCity on wicketstuff.org with Hudson and then do the necessary setup to allow wicketstuff developers access to it for initiating builds and viewing the projects status. I am willing to do all of the
Wicket stuff server maintenance
As you might have noticed, I've done a bit of preparing for our migration to hudson... Tomcat -> 7.0 Java -> 1.6 (otherwise tomcat doesn't run) I had to tweak the tomcat configuration to ensure that confluence would start up: added the missing drivers from the previous tomcat installation's lib folder, and fixed some startup parameters in catalina.sh Next: installing hudson. Martijn -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8
Re: Adding the flot project
Thank Michael. Does this work with other jquery integrations? What I mean is, will there be any conflicts? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Adding-the-flot-project-tp1909066p2297694.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: Wicket stuff server maintenance
installing hudson 1.367 doesn't seem to work properly. I get 404 errors on the homepage, users page and other pages. Asking around on #hudson on irc hasn't yielded a response... Martijn On Wed, Jul 21, 2010 at 6:24 PM, Martijn Dashorst wrote: > As you might have noticed, I've done a bit of preparing for our > migration to hudson... > > Tomcat -> 7.0 > Java -> 1.6 (otherwise tomcat doesn't run) > > I had to tweak the tomcat configuration to ensure that confluence > would start up: added the missing drivers from the previous tomcat > installation's lib folder, and fixed some startup parameters in > catalina.sh > > Next: installing hudson. > > Martijn > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8
Re: svn commit: r966409 - in /wicket/branches/wicket-1.4.x/wicket/src: main/java/org/apache/wicket/protocol/http/AbstractHttpSessionStore.java test/java/org/apache/wicket/protocol/http/pagestore/Dis
2010/7/21 > Author: jdonnerstag > Date: Wed Jul 21 20:43:25 2010 > New Revision: 966409 > > URL: http://svn.apache.org/viewvc?rev=966409&view=rev > Log: > fixed WICKET-2946 Exceptions raised in overridden sessionDestroyed() event > (of WebApplication class) are completely swallowed by the session-store > classes without even logging anything > Issue: WICKET-2946 > > Modified: > > > wicket/branches/wicket-1.4.x/wicket/src/main/java/org/apache/wicket/protocol/http/AbstractHttpSessionStore.java > > > wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/protocol/http/pagestore/DiskPageStoreTest.java > > Modified: > wicket/branches/wicket-1.4.x/wicket/src/main/java/org/apache/wicket/protocol/http/AbstractHttpSessionStore.java > URL: > http://svn.apache.org/viewvc/wicket/branches/wicket-1.4.x/wicket/src/main/java/org/apache/wicket/protocol/http/AbstractHttpSessionStore.java?rev=966409&r1=966408&r2=966409&view=diff > > == > --- > wicket/branches/wicket-1.4.x/wicket/src/main/java/org/apache/wicket/protocol/http/AbstractHttpSessionStore.java > (original) > +++ > wicket/branches/wicket-1.4.x/wicket/src/main/java/org/apache/wicket/protocol/http/AbstractHttpSessionStore.java > Wed Jul 21 20:43:25 2010 > @@ -223,8 +223,13 @@ public abstract class AbstractHttpSessio >catch (IllegalStateException e) >{ >// can safely be ignored > + log.warn("Error while invalidating Session > Store: Session already invalidated", e); > + } > + catch (Throwable e) > Any objections to make this "catch (Exception e)" ? I have bad experience with catching *Error's. > + { > + // can safely be ignored > + log.error("Error while invalidating Session > Store: ", e); >} > - >} >} > > > Modified: > wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/protocol/http/pagestore/DiskPageStoreTest.java > URL: > http://svn.apache.org/viewvc/wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/protocol/http/pagestore/DiskPageStoreTest.java?rev=966409&r1=966408&r2=966409&view=diff > > == > --- > wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/protocol/http/pagestore/DiskPageStoreTest.java > (original) > +++ > wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/protocol/http/pagestore/DiskPageStoreTest.java > Wed Jul 21 20:43:25 2010 > @@ -18,6 +18,10 @@ package org.apache.wicket.protocol.http. > > import junit.framework.TestCase; > > +import org.apache.wicket.Page; > +import org.apache.wicket.Session; > +import org.apache.wicket.protocol.http.WebApplication; > +import org.apache.wicket.util.tester.DummyHomePage; > import org.apache.wicket.util.tester.WicketTester; > > /** > @@ -71,4 +75,28 @@ public class DiskPageStoreTest extends T > >assertEquals(activeThreadsBefore - 1, activeThreadsAfter); >} > + > + /** > +* > +*/ > + public void testExceptionInSessionDestroy() > + { > + WicketTester tester = new WicketTester(new WebApplication() > + { > + @Override > + public void sessionDestroyed(String sessionId) > + { > + throw new NullPointerException("Error"); > + } > + > + @Override > + public Class getHomePage() > + { > + return DummyHomePage.class; > + } > + }); > + > + tester.startPage(DummyHomePage.class); > + Session.get().invalidateNow(); > + } > } > > >
Re: Wicket stuff server maintenance
OK seems to be a tomcat 7 incompatibility of hudson... Martijn On Wed, Jul 21, 2010 at 10:46 PM, Martijn Dashorst wrote: > installing hudson 1.367 doesn't seem to work properly. I get 404 > errors on the homepage, users page and other pages. > > Asking around on #hudson on irc hasn't yielded a response... > > Martijn > > On Wed, Jul 21, 2010 at 6:24 PM, Martijn Dashorst > wrote: >> As you might have noticed, I've done a bit of preparing for our >> migration to hudson... >> >> Tomcat -> 7.0 >> Java -> 1.6 (otherwise tomcat doesn't run) >> >> I had to tweak the tomcat configuration to ensure that confluence >> would start up: added the missing drivers from the previous tomcat >> installation's lib folder, and fixed some startup parameters in >> catalina.sh >> >> Next: installing hudson. >> >> Martijn >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.4 increases type safety for web applications >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8
Re: WebApplication.addIgnoreMountPath(String)
I forgot about this ... Actually this is org.apache.wicket.protocol.http.WebApplication.unmount(String) from Wicket 1.4. Don't know why this method is renamed ... Do we still need it ? 2010/7/19 Igor Vaynberg > you can by subclassing it... > > -igor > > On Mon, Jul 19, 2010 at 10:50 AM, Erik van Oosten > wrote: > > Presumably because you can not configure the wicket filter through code? > > > > I agree. The use case is thin. > > > > Regards, > >Erik. > > > > > > Op 19-07-10 18:24, Igor Vaynberg wrote: > >> > >> why do we need this? afaik in 1.4 wicket filter can be configured to > >> ignore paths > >> > >> -igor > >> > >> > > > > -- > > Sent from my SMTP compliant software > > Erik van Oosten > > http://day-to-day-stuff.blogspot.com/ > > > > > > >
Re: Wicket stuff server maintenance
Someone mentioned in users@ about a problem with relative paths in TC7 too. Maybe the examples wont work too. 2010/7/21 Martijn Dashorst > OK seems to be a tomcat 7 incompatibility of hudson... > > Martijn > > On Wed, Jul 21, 2010 at 10:46 PM, Martijn Dashorst > wrote: > > installing hudson 1.367 doesn't seem to work properly. I get 404 > > errors on the homepage, users page and other pages. > > > > Asking around on #hudson on irc hasn't yielded a response... > > > > Martijn > > > > On Wed, Jul 21, 2010 at 6:24 PM, Martijn Dashorst > > wrote: > >> As you might have noticed, I've done a bit of preparing for our > >> migration to hudson... > >> > >> Tomcat -> 7.0 > >> Java -> 1.6 (otherwise tomcat doesn't run) > >> > >> I had to tweak the tomcat configuration to ensure that confluence > >> would start up: added the missing drivers from the previous tomcat > >> installation's lib folder, and fixed some startup parameters in > >> catalina.sh > >> > >> Next: installing hudson. > >> > >> Martijn > >> > >> -- > >> Become a Wicket expert, learn from the best: http://wicketinaction.com > >> Apache Wicket 1.4 increases type safety for web applications > >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 > >> > > > > > > > > -- > > Become a Wicket expert, learn from the best: http://wicketinaction.com > > Apache Wicket 1.4 increases type safety for web applications > > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 > > > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >
Re: WebApplication.addIgnoreMountPath(String)
i dont see why -igor On Wed, Jul 21, 2010 at 2:15 PM, Martin Grigorov wrote: > I forgot about this ... > > Actually this > is org.apache.wicket.protocol.http.WebApplication.unmount(String) from > Wicket 1.4. > Don't know why this method is renamed ... > > Do we still need it ? > > 2010/7/19 Igor Vaynberg > >> you can by subclassing it... >> >> -igor >> >> On Mon, Jul 19, 2010 at 10:50 AM, Erik van Oosten >> wrote: >> > Presumably because you can not configure the wicket filter through code? >> > >> > I agree. The use case is thin. >> > >> > Regards, >> > Erik. >> > >> > >> > Op 19-07-10 18:24, Igor Vaynberg wrote: >> >> >> >> why do we need this? afaik in 1.4 wicket filter can be configured to >> >> ignore paths >> >> >> >> -igor >> >> >> >> >> > >> > -- >> > Sent from my SMTP compliant software >> > Erik van Oosten >> > http://day-to-day-stuff.blogspot.com/ >> > >> > >> > >> >
Re: svn commit: r966409 - in /wicket/branches/wicket-1.4.x/wicket/src: main/java/org/apache/wicket/protocol/http/AbstractHttpSessionStore.java test/java/org/apache/wicket/protocol/http/pagestore/Dis
> > > + catch (Throwable e) > > > Any objections to make this "catch (Exception e)" ? > I have bad experience with catching *Error's. > > I agree. If I remember correctly, "Effective Java, 2nd edition" suggests not to catch Throwable. I could be wrong. I like to stick at Exception as well. -- Jeremy Thomerson http://www.wickettraining.com
Re: Wicket stuff server maintenance
Why do we want already tomcat 7, which is still in a first? beta? Why not the latest stable 6? Is it really faster and better? (I havent really looked into 7 yet will do asap) - Original message - > OK seems to be a tomcat 7 incompatibility of hudson... > > Martijn > > On Wed, Jul 21, 2010 at 10:46 PM, Martijn Dashorst > wrote: > > installing hudson 1.367 doesn't seem to work properly. I get 404 > > errors on the homepage, users page and other pages. > > > > Asking around on #hudson on irc hasn't yielded a response... > > > > Martijn > > > > On Wed, Jul 21, 2010 at 6:24 PM, Martijn Dashorst > > wrote: > > > As you might have noticed, I've done a bit of preparing for our > > > migration to hudson... > > > > > > Tomcat -> 7.0 > > > Java -> 1.6 (otherwise tomcat doesn't run) > > > > > > I had to tweak the tomcat configuration to ensure that confluence > > > would start up: added the missing drivers from the previous tomcat > > > installation's lib folder, and fixed some startup parameters in > > > catalina.sh > > > > > > Next: installing hudson. > > > > > > Martijn > > > > > > -- > > > Become a Wicket expert, learn from the best: > > > http://wicketinaction.com Apache Wicket 1.4 increases type safety > > > for web applications Get it now: > > > http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 > > > > > > > > > > > -- > > Become a Wicket expert, learn from the best: http://wicketinaction.com > > Apache Wicket 1.4 increases type safety for web applications > > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 > > > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8