all questions are fine. 1) Nexus installation is out of questions - I can't share specifics but "Stone Age" approach is the best I can do at the moment. 2) No IDE involved - we use RAD (IBM's take on Eclipse) but it's on Windows. A Unix box does all the builds through maven/shell scripts. CVS is the source control of choice. 3) I can't change existing projects; Besides IDE compiles the projects locally (no Maven involved) but releases are made through a Unix box. 4) In essence I run the following command from the level of parent pom: mvn scm:checkout compile dependency:copy
I need the last step to create artifacts with names that match M1 (no versioning of jars/wars/ears etc) Then a shell script pics up the results and copies them to a release server. Snapshots are compiled hourly - automatically. Releases are controlled differently and take place 4-5 times a month. I hope it helps. Thanks, Dave On Thu, Jun 24, 2010 at 1:10 PM, Ron Wheeler <[email protected] > wrote: > On 24/06/2010 2:02 PM, D D wrote: > >> Hello, >> >> I've converted projects from M1 to M2 and now have just few decisions to >> make. >> >> I use parent pom.xml to hold all things that are shared like version, >> groupId etc. Parent pom has modules and expects the module projects to be >> as >> subdirectories of the parent pom location. >> >> Every module has its own pom.xml file and here comes my question: *should >> a >> module's pom.xml be stored with the parent pom project or the actual >> module >> projects?* >> >> If I store the xml files with the parent pom project then I can check out >> just parent project and have modules checkout subsequently by using maven. >> >> If I store them with the projects then I have to write a shell script to >> check out the projects from terminal. >> >> Also since *parent pom is installed in my local repository is there** a >> way >> to copy it to an arbitrary location using maven command?* >> * >> * >> I am open to all suggestions and "best practices" guidelines. >> * >> * >> Thanks, >> Dave >> >> >> > > 1) Do you have a repository like Nexus. If not, get one. It adds a level of > transparency to Maven that really helps. > 2) You did not mention, your IDE and version control system. That may make > a difference in how you approach things. > 3) You did not mention the size of your development team which has a big > impact on how you structure projects. > 4) You did not mention how you prepare and release new versions of your > software and how robust your deployments needed to be. Frequency of new > releases makes a difference. > > Sorry for the ratio of advice to questions. > > Ron > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
