CODEWITHSUNDEEP
mavenmaven-2maven-3nexusartifactory
Tekdev
Tekdev

Reputation: 448

Distinguishing maven releases/snapshots from trunk than the ones from branches when getting latest dependencies

I am working on project to automate maven releases for large set of inter-dependent modules. First the task involves getting the latest versions for internal dependencies. Than order the builds in a way every project is built before it’s needed. Hopefully that combination will get me to my goal of one click bulk release.

However my biggest problem is: We branch projects from time to time and we do releases/snapshots to Nexus repo manager from that branch. Obviously because the groupId and ArtifactId are the same as the trunk- Snapshots/Releases from trunk and one from branches end up in the same place in nexus.

In a scenario where we have projectA with a trunk version 1.1.x And projectB → projectA version 1.1.x So if I use the version-plugin to get the latest dependencies for B, I will get the latest. (perfect)

However if I later branch ProjectA with a version 1.2.0 and add changes that I don’t want projectB to pick up or could potentially break it. Now next time I run projectB and I use the version plugin to get the latest , The plugin will get the branch version (1.2.0) for ProjectA, as it’s numerically the latest. And there you go, projectB build fails.

I have so far tried adding a classifier to the artifact to distinguish between the two but I later realised the plugin does not act upon the classifier.

This give me so much frustration and will appreciate any hints or advice

Upvotes: 2

Views: 853

Answers (2)

Manfred Moser
Manfred Moser

Reputation: 29912

The typical approach to solve this problem is to use branch names as version classifiers and that approach works for all scenarios I have seen so far. What problem did you have with this?

Upvotes: 1

MariuszS
MariuszS

Reputation: 31577

Simple use proper/diffrent artifact names for branches. You can automatically create proper artifact names Maven Release plugin

mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT

Upvotes: 1

Related Questions