> Is there any way to set up multi-module projects so that they can share a > module, and both projects can detect when that module's source code is > out-of-date? Thanks,
Well this is the first obvious approach: > \- Simple Parent Project > +- Simple Weather API > +- Simple Web Application Project > +- Simple Web Application Project 2 or this: \- Shared parent project > +- Simple Parent Project > -- Simple Weather API > -- Simple Web Application Project > +- Simple Parent Project 2 > -- Simple Web Application Project 2 Or you could use a "builder pom" that some people advocate, which looks something like: \- builder pom (modules "..\parent1" and "..\parent2") \- Simple Parent Project +- Simple Weather API +- Simple Web Application Project \- Simple Parent Project 2 +- Simple Web Application Project 2 One note, I personally do not like/use the third approach myself. I would tend towards the first one if you require both projects to "detect when a shared module is out-of-date" as you have stated. The fact that the projects are "completely independent" is not particularly important IMO. Another option would be to simply break the API out as its own project. Then changes would be "detected" by no one, and you would have to forcibly update/rebuild the webapps on an as-needed basis. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
