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]
