> I have a project depending upon a couple of others. (the classic beginning of a > question in the forum:-) > > My existing build system (fully Ant-based) is organized in the next way. If any > changes since the previous build have occured in CVS for a certain project than a > new release is built its verison number is calculated the module is labeled (tagged) > and the newly fleddged jar (war) is deployed (I omit non essential style checking, > unit testing and report building activity). Our label policy is a bit complicated > (we distinguish between internal releases and ones going to QA). This workflow works > for all modules with an exception that in case of superproject the script checks for > CVS activity also of the modules it depends on. > > I wanna implement the same workflow by Maven. After reading the forum and the docs I > came to a guess how to do it but it doesn't look elegant at all. > > For a primary project (one that doesn't depend upon others) I have to check that > changes in CVS occured and if so build a new version. Getting the source and parsing > it may be done by Jelly and Ant together I guess. Each release has its onw unique > name (module-version.jar). > > For a dependent project the problem is project.xml file that has to contain exact > version nubmers of the projects it depends on. Is there an easy way to do it? Maybe > my algorithm doesn't suit to Maven's philosophy?
