> For your last question, if you are using Eclipse Kepler or better, the > maven integration should be good enough to allow workspace resolution of > the other modules, as long as they are open. > i.e. you can change something in one module and have the dependent modules > pick up the changes, without needing to do a separate maven build or > install. This even works between overlays and the main web app project. >
I've been expecting it should work that way, but it doesn't. Unless I perform "mvn clean install" inside the module project, I receive build error "[WARNING] The POM for my.package:module-name:jar:0.0.1-SNAPSHOT is missing, no dependency information available" I suppose it has something to do with external Maven installation that I'm using instead of embedded one, but I'm not sure. > On Wed, Jul 9, 2014 at 4:38 PM, Ilya Obshadko <ilya.obsha...@gmail.com> > wrote: > > > I would like to modularize my application into several modules, so that > > each one of them would be a separate Maven artifact. I'm trying to > > reproduce what I can borrow from tapestry-upload module source, but still > > have questions: > > > > - component that was moved into separate module can't be loaded by main > > application using standard namespace; is there any way to fix that? (that > > is, <t:mycomponent/> results in UknownValueException); > > contributeComponentClassResolver() (like in tapestry-upload) doesn't help > > (or I just use it incorrectly) > > > > - is that possible to run the whole thing within Eclipse without having > to > > install 'module' project into local repository? > > > > Thanks in advance. > > > > -- > > Ilya Obshadko > > > -- Ilya Obshadko
