The use case for this is that we have a two step process for shipping test releases of product P to customers A and B. Step 1 builds the snapshot artifact for P in a separate maven module. Step 2 then has a maven umbrella project containing many modules - one pr product pr customer - responsible for assembling the exact bits to go to that customer, here it would be P_A for product P to customer A and P_B for product P to customer B (and many more like Q_A, Q_B, and Q_C) and for simplicity's sake we point Jenkins to the root of the umbrella project which works very nicely except we would like for only P_A and P_B to be rebuilt when P is updated instead of all modules under the umbrella project.
The use case for this is that we have a two step process for shipping test releases of product P to customers A and B. Step 1 builds the snapshot artifact for P in a separate maven module. Step 2 then has a maven umbrella project containing many modules - one pr product pr customer - responsible for assembling the exact bits to go to that customer, here it would be P_A for product P to customer A and P_B for product P to customer B (and many more like Q_A, Q_B, and Q_C) and for simplicity's sake we point Jenkins to the root of the umbrella project which works very nicely except we would like for only P_A and P_B to be rebuilt when P is updated instead of all modules under the umbrella project.