Hi, i'm new to that list and just doing my first steps with Maven 2.0.1, planning to use it in production.
Currently there's a deployment workflow mainly based upon ant and i have some questions how to switch to a maven based workflow. The current workflow in short terms, many projects, extensive dependencies beyond those projects = step 1 = Build (without any JUnittests) that creates artifacts like jarfiles and ear's out of sources lying in a cvs repository (soon to be changed to ClearCase UCM) Every served project has it's own build script in cvs, edited by project when new packages appear ... The build process does an update of those ant scripts before starting the build. step 2 = checkin of created artifacts in a central repository workin with Base ClearCase (maybe changing to UCM soon) A modul in cvs is mirrored as a folder in a ClearCase Vob step1 and step2 on a Windows Box step 3 = transfer to the runtime environment on a Unix Box (AIX), where Clients can pull the new stuff via a self written update mechanism. step 2 is done against the rule, that everything that can be rebuilt from the sources should not be put under version control. The purpose for that was to enable a quick rollback if updates are erroneous. The artifacts could be rebuilt, but if build script has changed in the meantime, how to assure that the rebuild wents exactly the same; have to store the build script somehow. Questions = is ClearCase UCM fully supported ? step 1 = could be achieved with Maven plugins step 2 = as far as i've learned til now, Maven has it's own repository, where artifacts are stored. So i could get rid of the central repository, but how to achieve quick rollback with the local repository of Maven ? If i want to do a whole rebuild of an older version before rollback, what's the best practice to store the buildscripts ? Also in local Maven repository ? step 3 = could be achieved with Maven plugins So my main question is about eliminating the central repository, as for several reasons it's error-prone, and substitute it with Maven functionality. Any hints ? Best practices ? Regards, Gilbert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
