On release-finish, only deploy a specified submodule

[Oskar Wyke]

Hello,

We are building a parent project that has multiple sub-modules. One of these submodules assembles the binary that is distributed. This is also the only artifact the should be stored in the binary repository (in our case Artifactory) when creating a release.

As default, JGitFlow deploys all built artifacts, we don´t want that. What I´ve tried is to set noDeploy=true in the parent pom and then override this property in the sub module pom.

This does not work as I intended since no artifacts get deployed, but instead installed in the local repository. Maybe I´ve missed something obvious?

Is there any other way I can achive this functionality?

Part of configuration in parent pom (should not be deployed):

<profile>
         <id>release</id>
         <build>
             <plugins>
                 <plugin>
                     <groupId>external.atlassian.jgitflow</groupId>
                     <artifactId>jgitflow-maven-plugin</artifactId>
                     <configuration>
                          ...
                         <noDeploy>true</noDeploy>
                         ...
                     </configuration>
                 </plugin>
              </plugins>
         </build>
</profile>

                

Part of configuration in module pom (should be deployed):

<profile>
       <id>release</id>
           <plugins>
               <plugin>
                   <groupId>external.atlassian.jgitflow</groupId>
                   <artifactId>jgitflow-maven-plugin</artifactId>
                   <configuration combine.self="override">
                       <noDeploy>false</noDeploy>
                   </configuration>
               </plugin>
           </plugins>
       </build>
</profile>

/Oskar

[Jeffrey Bell]

One way to do this would be to add <skip>true</skip> to the maven-deploy-plugin in the parent pom, and override that in the binary distribution project.