In my mind... those are governance issues and are inherent in the decision to port to maven. Maven will simplify your life in terms of code and dependency management and if those legacy projects are still in active development - it's not an unadvisable port.
For the most part, your codebase should not change but your file system structure will. Maven has no imposition on code itself. It only asks that your packages reside in the designated folder for packaging. Your over all project structure should port cleanly into maven modules which will reduce your port into simply creating the appropriate project/module structure to house your project. If you are asking for help in how to set up your project within the maven structure... the information given (based on the limited descriptions provided) are the best courses of action for moving forward. I do not recommend getting fancy with the file system structure - as Steven stated below - you will run into all sorts of complications when trying to get various plugins to work and will have to do an exurbanite amount of configuration for your project. Such things increase your risk of error significantly as well as substantially increase your development times - effectively negating the benefits of using such a system to begin with. Keith -----Original Message----- From: dennis.mendel...@rbs.com [mailto:dennis.mendel...@rbs.com] Sent: Tuesday, September 22, 2009 1:37 PM To: users@maven.apache.org Subject: RE: Help with (sibling directory) modules I care, because the legacy nature of the project means that any changes I make to the existing structure of codebase on filesystem entails a lot of thought, and risks a veto. This is surely not an uncommon scenario. I understand what is involved in, and (directly) implied by, declaring one project to be parent of another. Dennis -----Original Message----- From: Barlow, Keith [mailto:keith_bar...@cable.comcast.com] Sent: 22 September 2009 18:09 To: Maven Users List Subject: RE: Help with (sibling directory) modules With all due respect, why do you care? The parent project is only a POM... It effectively declares the structure of the project. If there is a core piece of logic that all other modules are built around, you define a module for that logic and then declare it as a dependency of all other modules. I think you are misinterpreting the role of the parent - there is no code involved. Keith <snip> ************************************************************************ *********** The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority. This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate. Visit our website at www.rbs.com ************************************************************************ *********** --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
