Use Maven's managed dependencies#269
Merged
Merged
Conversation
Collaborator
|
Hi tomasz, |
manuel-mauky
added a commit
that referenced
this pull request
Jun 16, 2015
Use Maven's managed dependencies
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Declaring the
mvvmfx-*artifacts inmvvmfx-parent's managed dependencies gives users a centralised version management for allmvvmfx-parentdescendants. It's extensively explained in Maven docs.But simply speaking, it puts the required version of all
mvvmfx-*artifacts in one place. Users now can declare dependencies:Although all other
mvvmfx-*artifacts are listed in<managedDependencies>only the ones specifically listed in<dependencies>are actually used.There is one drawback to this. The
<scope>import</scope>attribute is only available in Maven 2.0.9 or later.