Folks; not sure whether this is a "common" use case, I wonder what's a good way to have the following scenario done. We handle our projects using maven2, and we are used to have things split up:
- There's a "core" project (jar) of the application which includes commonly used classes and interfaces needed in all other applications. - There are some "components" projects (jars, as well), depending upon "core", used in some of the business applications. - There are a bunch of, say, war artifacts offering exposing web interfaces or web services, depending upon various "components". My problem, by now, is that, in case of some change tthat cross these module boundaries, I have to rebuild altogether "core", a few "components" packages and the war artifact relying upon them. My question is whether there is some way to, in case these projects are independent, "abuse" maven to have, say, "core" and a set of "components" automatically built and installed along with (and possibly before) building the war artifact depending upon them? Is there a common way of doing so, or should I reconsider my project structure? TIA and best regards, Kristian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
