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]
