Is Jenkins maven building dependent projects?

Question

I have a project with several modules that use the modules "Application A" and "Application B" (this is a separate module with its own memory file, but not connected to each other).

In the dev loop, each of these modules has its own function branch. Let's say

Application A --- Master \ - Feature 1 Application B --- Master \ - Feature 1 

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

Appendix B uses Appendix A as a jar. And it is determined depending on pom.

Now both teams are working on a feature branch, they say "Feature 1". What is the best way to set up Jenkins builds so that Build Work for Application B can use the latest jar from the Feature 1 branch of application A.

This function 1 is not allowed to deploy its artifacts to the maven repository.

Somehow I want the jar from the Application A Feature 1 branch to be provided as the correct dependency for application B?

Answer 1

Why don't you enable feature1 features for deployment to the maven repository?

If it does not mix unstable and stable code in a repo, how about setting up a second maven repository only for unstable code?

Answer 2

Shouldn't I fix this with the new version and create snapshots? For your new feature, you are creating a snapshot for an upcoming specific version. (e.g. 01.01.00.001-SNAPSHOT). The wizard still has a different version (for example, 01.00.00.055), and this will not be associated with this snapshot of the new version. Although the function branch in your other application may use version 01.01.00.001-SNAPSHOT as a dependency.