Take the 2-minute tour ×

I have a project with multiple modules say "Application A" and "Application B" modules (these are separate module with its own pom file but are not related to each other).

In the dev cycle, each of these modules have its own feature branch. Say,

 Application A --- Master
                   - Feature 1

 Application B --- Master
                   - Feature 1

Say Application A is independent and has its own release cycle/version.

Application B uses Application A as a jar. And is defined in its pom dependency.

Now, both teams are working on a feature branch say "Feature 1". What is the best way to setup Jenkins build such that, Build job for Application B is able to use the latest jar from "Feature 1" branch of Application A.

Given Feature 1 is not allowed to deploy its artifacts to maven repository.

Somehow I want the jar from Application A's Feature 1 branch to be supplied as the correct dependency for Application B?

share|improve this question
add comment

1 Answer

Why wouldn't you allow feature1 to deploy to the maven repository?

If it's about not mixing unstable and stable code in the repo, how about setting up a second maven repository only for unstable code?

share|improve this answer
add comment

Your Answer


