How to specify maven s distributionManagement organisation wide

Question

I m trying to figure out how to organize many  around 50   maven2 projects  so that they can deploy into a central nexus repository  When using the mvn deploy goal  one does need to specify the target in the distributionManagement tag like this    lt distributionManagement gt      lt repository gt         lt id gt nexus-site lt  id gt           lt url gt http   central nexus server lt  url gt      lt  repository gt   lt  distributionManagement gt    Now  i don t want every single pom xml  of those 50   to contain this block over and over again  My first though would be the settings xml file  but it seems it is not possible  by design  to define it there   So  the first question would be  why is that the case   If it would be possible i could specify it in the settings xml in the maven2 distribution  which could be distributed to all developers   The only possible solution i ve found was to create an organisation-wide master-pom project  that does contain these settings  and make all other pom xml depend on this master-pom via  lt parent gt  tag  But this looks kind of strange in multi-module builds   - master configuration POM  pm  - Project 1 parent pom  p1 with module 1 and module 2 as modules      - Project 1 module pom  with pm as parent      - Project 2 module pom  with pm as parent    Usually i read in all documentation that the module poms should use the parent pom  not some different one  But after reading the maven website about Inheritance v  Aggregation it is written that it is indeed possible   One problem i found was with the maven site generation  which does seem to have problems with this setup  modules does not get linked correctly if they have no direct back-reference   So  is this a valid approach   Any other  more obvious  simpler solution to the problem

User · Answer

Regarding the answer from Michael Wyraz  where you use alt DeploymentRepository in your settings xml or command  on the line  be careful if you are using version 3 0 0-M1 of the maven-deploy-plugin  which is the latest version at the time of writing   there is a bug in this version that could cause a server authentication issue  A workaround is as follows   In the value  releases  default  https   YOUR NEXUS URL releases  you need to remove the default section  making it  releases  https   YOUR NEXUS URL releases  The prior version 2 8 2 does not have this bug

User · Answer

The best solution for this is to create a simple parent pom file project  with packaging  pom   generically for all projects from your organization    lt  xml version  1 0  encoding  UTF-8   gt   lt project xmlns  http   maven apache org POM 4 0 0  xmlns xsi  http   www w3 org 2001 XMLSchema-instance       xsi schemaLocation  http   maven apache org POM 4 0 0 http   maven apache org maven-v4 0 0 xsd  gt       lt modelVersion gt 4 0 0 lt  modelVersion gt        lt groupId gt your company lt  groupId gt       lt artifactId gt company-parent lt  artifactId gt       lt version gt 1 0 0-SNAPSHOT lt  version gt       lt packaging gt pom lt  packaging gt        lt distributionManagement gt           lt repository gt               lt id gt nexus-site lt  id gt               lt url gt http   central nexus server lt  url gt           lt  repository gt       lt  distributionManagement gt    lt  project gt    This can be built  released  and deployed to your local nexus so everyone has access to its artifact   Now for all projects which you wish to use it  simply include this section    lt parent gt     lt groupId gt your company lt  groupId gt     lt artifactId gt company-parent lt  artifactId gt     lt version gt 1 0 0 lt  version gt   lt  parent gt    This solution will allow you to easily add other common things to all your company s projects  For instance if you wanted to standardize your JUnit usage to a specific version  this would be the perfect place for that   If you have projects that use multi-module structures that have their own parent  Maven also supports chaining inheritance so it is perfectly acceptable to make your project s parent pom file refer to your company s parent pom and have the project s child modules not even aware of your company s parent   I see from your example project structure that you are attempting to put your parent project at the same level as your aggregator pom  If your project needs its own parent  the best approach I have found is to include the parent at the same level as the rest of the modules and have your aggregator pom xml file at the root of where all your modules  directories exist   - pom xml  aggregator      - project-parent     - project-module1     - project-module2   What you do with this structure is include your parent module in the aggregator and build everything with a mvn install from the root directory   We use this exact solution at my organization and it has stood the test of time and worked quite well for us

User · Answer

There s no need for a parent POM   You can omit the distributionManagement part entirely in your poms and set it either on your build server or in settings xml   To do it on the build server  just pass to the mvn command   -DaltSnapshotDeploymentRepository snapshots  default  https   YOUR NEXUS URL snapshots -DaltReleaseDeploymentRepository releases  default  https   YOUR NEXUS URL releases   See https   maven apache org plugins maven-deploy-plugin deploy-mojo html for details which options can be set   It s also possible to set this in your settings xml   Just create a profile there which is enabled and contains the property   Example settings xml    lt settings gt           lt profiles gt       lt profile gt         lt id gt nexus lt  id gt         lt properties gt           lt altSnapshotDeploymentRepository gt snapshots  default  https   YOUR NEXUS URL snapshots lt  altSnapshotDeploymentRepository gt           lt altReleaseDeploymentRepository gt releases  default  https   YOUR NEXUS URL releases lt  altReleaseDeploymentRepository gt         lt  properties gt       lt  profile gt     lt  profiles gt      lt activeProfiles gt       lt activeProfile gt nexus lt  activeProfile gt     lt  activeProfiles gt    lt  settings gt    Make sure that credentials for  snapshots  and  releases  are in the  lt servers gt  section of your settings xml  The properties altSnapshotDeploymentRepository and altReleaseDeploymentRepository are introduced with maven-deploy-plugin version 2 8  Older versions will fail with the error message  Deployment failed  repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository id  layout  url parameter   To fix this  you can enforce a newer version of the plug-in            lt build gt             lt pluginManagement gt               lt plugins gt                 lt plugin gt                   lt artifactId gt maven-deploy-plugin lt  artifactId gt                   lt version gt 2 8 lt  version gt                 lt  plugin gt               lt  plugins gt             lt  pluginManagement gt           lt  build gt

[java] How to specify maven's distributionManagement organisation wide?

Examples related to java

Examples related to maven

Examples related to deployment

Examples related to maven-2

Examples related to nexus