Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolving Dependencies #1

Open
e-moshaya opened this issue Dec 5, 2018 · 0 comments
Open

Resolving Dependencies #1

e-moshaya opened this issue Dec 5, 2018 · 0 comments

Comments

@e-moshaya
Copy link

Hi,

I would love to use this plugin for our workflow. However, in my CI, I have a pre-build stage to update all internal project dependencies to the latests snapshots/release versions. for feature branches, update to latest snapshot, for master branches update to latest release versions:

mvn -e -U versions:use-latest-snapshots -DgenerateBackupPoms=false
-DallowSnapshots=true -Dincludes=groupid*:* -DserverId="feature-branch-repo"

mvn -e -U versions:use-latest-versions -DgenerateBackupPoms=false
-DallowSnapshots=false -Dincludes=groupid*:* -DserverId="release-branch-repo"

If I have project A (library) versioned using your plugin feature-featurebarnch-SNAPSHOT, this project is a dependency for projectb which also got versioned using the same convention feature-featurebarnch-SNAPSHOT.
my question to you is, is there a way to get the downstream project b to update the project a dependency to use the latest snapshot from the same feature branch name and if no versions available from feature branch or branch does not exist, then use the latest release version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant