Hello Oliver (and everyone else),
can you tell us who do you define a "bigger project"?
Well, bigger project in this case would be starting with two web applications, with some shared code (thus best put into separate modules that get developed along the main applications). More applications, also sharing code with the other applications, are likely in the future.
All applications get deployed to tomcat servers (some applications might share the same server, others might have different servers - and of course, there are test servers and pre-release servers to consider as well).
We are currently a SCRUM team, so normally only one application will be actively developed in one development cycle ("sprint"), but after each cycle , we want to release a new version of the currently developed application and, if they were modified, also new versions of the shared code modules.
Deployment should be automatic, not requiring many steps, but obviously it gets a little bit complicated since, for example, when we want to release an RC1, we would also (preferably) automatically release an RC1 of the shared code modules that were modified, too. If they weren't modified, we would preferably not release new versions of the shared code, but that point if debatable.
The whole thing is on GIT, currently in one repository, but of course, there are arguments for using separate repositories for the applications and the shared code. But my question aims more in the Maven direction (obviously), because there seem to be a lot of articles about the basics, but not many about more complex topics like handling more complex projects... (Or I am simply missing them).
Regards, Flo --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
