I agree with both of those. I'm not real sure either regarding the etiquette - that's been my dilemna throughout. That's the reason I started so many vote threads. I think both of those things would be acceptable, though. A common build setup was the goal of this. I'd like to also see us use a common version of many standard libraries at some point (commons, logging etc), but I don't think it's critical right this moment. At least they're all against a common Wicket version.
If you supply a patch, I'll apply it. Or you can just do it if you want. You would be making sure each folder also had svn:ignore for .classpath, .project and target folder? Jeremy Thomerson http://www.wickettraining.com -- sent from a wireless device -----Original Message----- From: Ryan McKinley <[EMAIL PROTECTED]> Sent: Sunday, November 30, 2008 10:33 AM To: users@wicket.apache.org Subject: Re: [discuss] Organizing Wicket Stuff / Regular Release Schedule? Great work! Its really looking good! Two more suggestions: 1. Add the maven-jetty-plugin the the root pom. It would be nice if 'mvn jetty:run' works for all the examples. 2. Remove all eclipse projects (.project .classpath) from svn and add the 'maven-eclipse-plugin' to the root project. I can make patches for these changes if you like... but i'm not totally clear on the etiquette for wicketstuff. Is someone (you?) allowed to apply a patch that affects build for many projects? ryan On Nov 30, 2008, at 1:16 AM, Jeremy Thomerson wrote: > PS - Good suggestion - this was included. Take a look at: > https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-core > > -- > Jeremy Thomerson > http://www.wickettraining.com > > On Tue, Nov 25, 2008 at 4:32 PM, Ryan McKinley <[EMAIL PROTECTED]> > wrote: > >> I don't know if this has already been discussed, but another part >> of the >> cleanup that would be nice is to group the main project and the >> example >> project into a folder with a common parent pom. >> >> For example, I find the layout of: >> >> https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/inmethod-grid/ >> >> much easier to use/maintain then the apparent standard of >> /wicketstuff-project & /wicketstuff-project-example >> >> https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push/ >> >> https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push-examples/ >> >> one key thing about this change is that mvn eclipse:eclipse makes the >> example project depend on the core project >> >> perhaps this could be added to the 'organize' task? >> >> ryan >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
