Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.0-alpha-1
-
Component/s: reporting
-
Labels:None
-
Number of attachments :
Description
repository tool to ensure that transitive dependencies will work.
we basically need to know that every artifact that
is referenced in one POM is actually in the repository along with its
POM. We need to know that the dependency relationships among
all artifacts in the repository form a closed set. otherwise the
transitive dependency mechanism in m2 will break and we need to be wary
of this. eventually i would like to create graphical representations of
the dependencies amongst projects but this can come later.
Issue Links
- is duplicated by
-
MNG-335
graph dependencies found vs. needed on convert, report missing
-
Note: that such check must span multiple repositories: An organization may publish their artifacts to a their private repository, but the artifacts could have dependencies both in the private and public repositories.
If the scan were performed on a single repository only, dependencies from public repository would have to be replicated in private repository to pass the check, which would a waste of bandwidth and resources.