Great idea! Yes. I have not nested any projects three deep in the past,
but it should work. Has anybody else tried this?
It would be:
wicket-stuff-parent
-- wicket-foo
-- wicket-foo-core
-- wicket-foo-examples
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]
>
>
--
Jeremy Thomerson
http://www.wickettraining.com
