Though I read on a separate thread on this list (http://www.nabble.com/Top-level-POM-behaviour-t1825699.html#a4980080) that doing a module based build is not working for separated projects. That is why I didn't put a modules section in the parent project.
Here's the quote from Alexandre: ---- begin quote ---- Modules are meant to be built from the top project so you can work on all of them at the same time. Don't try to build them separatly because it won't work. If it's not what you want and you prefer compiling each project separately, you should stick to normal SNAPSHOT dependencies. ---- end quote ---- In our case, each project may have a separated build: wicket-spring is a self contained project with its own website etc. Am I not grokking something here? Should I add a modules section to my parent project? Martijn On 7/1/06, Andrew Williams <[EMAIL PROTECTED]> wrote:
I may be wrong, but if your parent is, as in the book, a pom packaged artifact with a module list then doing a release at that level should prompt (with sensible defaults) the release of all the modules. Andy On Fri, 2006-06-30 at 21:29 +0200, Martijn Dashorst wrote: > All, > > I've updated the structure of my projects that depend on one another > to the structure as proposed in the better builds with maven book. > > The one problem I have with this way of building is the link to the > parent project: > > <parent> > <groupId>wicket</groupId> > <artifactId>wicket-parent</artifactId> > <version>1.2-SNAPSHOT</version> > </parent> > > Now I have to update all projects to perform a release of say version > 1.2.1. Or is there a better way? > > BTW. All projects use snapshot dependencies as adviced earlier on this > mailinglist. > > Martijn > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Download Wicket 1.2 now! Write Ajax applications without touching JavaScript! -- http://wicketframework.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
