title: Best practices for storing maven artifacts in nexus
body: <p>In my company we have teams working on services which are built using maven pom's and gradle build scripts. The problem I have is that when the team's build their web applications, the jar files that get's created by one team member needs to be available for other team members in their pom files.</p>
  
  <p>What we were thinking was to have a local nexus repo and then push the built jar files to nexus so that when any other team member builds they also can refer the same jar file. </p>
  
  <p>However this could lead to versioning problems as two team members could be generating the same jar file if they change different files in the same project.</p>
  
  <p>What I would like to know is are their any best practices in doing these types of builds and versioning.</p>