Skip to end of metadata
Go to start of metadata

Maven Best Practice Guide

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean vel quam nec urna mollis malesuada. Praesent egestas interdum tempus. Maecenas et nibh enim. Ut tristique, tortor sit amet mollis accumsan, neque purus gravida lorem, et porttitor sem justo eget sem. Pellentesque scelerisque augue elementum nisi vulputate dictum. Sed et mi lacus, sit amet facilisis diam. Suspendisse potenti. Nunc ut nulla velit, vel varius massa. Donec viverra nisi quis ligula tristique vitae tempor eros egestas. Morbi fermentum posuere ultricies. Nunc dui odio, auctor nec interdum et, volutpat ut mi. Proin purus ligula, euismod accumsan tempus in, semper ut massa. Nunc in magna vitae odio tempus ornare. Donec quam nunc, eleifend sed adipiscing eu, sagittis nec mi.

  • No labels

1 Comment

  1. Best Practices with Git

    From a previous discussion on users@maven.apache.org there was some question of how to set up your git repositories according to your project structure. There seems to be two basic answers:

    1. It is best to keep your entire project and modules within the same git repository, provided all the module versions are in sync with the project version, that is you release all artifacts in the project with the same version.
    2. If you have a project with modules that have different release versions, then you should have a separate git repository for those artifacts.
      1. One strategy is to break your project up into sub-projects, where all the modules in the sub-project share the same release version.
      2. In the worse case, you would have a separate git repository for every artifact/module, which is harder to maintain, but possibly necessary if each has a separate release life-cycle.