> first I'd ask, why do you hesitate to install the Libraries to your local > repository?
I am in prototyping phase and being new to wicket it is a mess ;) I consider it more flexible and less messy not to install such jars into maven repository - their expected lifetime is too short to be worth the trouble. > If you want to compile them all in one rush a parent module would have to be > created, the ones of packaging type 'pom'. Though I'm not sure that this > parent > module could be configured to compile all three modules and run the web-app in > one 'mvn jetty:run' call. I tried creating a parent pom, but the jetty plugin seems to be trying to deploy all projects as web projects even though only the workspace/Wicket-Quickstart-App -module is a web app. Should I exclude them somehow? <modules> <module>workspace/Wicket-Quickstart-App</module> <module>workspace/UtilityLibrary1</module> <module>workspace/UtilityLibrary2</module> </modules> [INFO] Configuring Jetty for project: Unnamed - MyProject:UtilityLibrary2:jar:0.0.1 [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Webapp source directory ..\UtilityLibrary2\src\main\webapp does not exist > Also even when a parent module is set up each module still would be > installed into the local maven repository. I guess they'd be installed only if I call the install target? I wouldn't expect the jetty:run target to perform an install. I am not sure about this. > The best reason for a parent module is that it allows to manage the outbound > dependencies of the modules to other libraries. Ok. Thank you. Now I just need help with the parent pom not to assume my utility projects for web applications ;) Anyone? ** Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
