[
https://jira.codehaus.org/browse/MVERIFIER-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MVERIFIER-1.
---------------------------------------
Resolution: Won't Fix
This is not related to maven-verifier-plugin.
> Verify that all dependencies are available in one of the remote repositories
> ----------------------------------------------------------------------------
>
> Key: MVERIFIER-1
> URL: https://jira.codehaus.org/browse/MVERIFIER-1
> Project: Maven Verifier Plugin
> Issue Type: New Feature
> Reporter: Geoffrey De Smet
>
> One problem I 've encountered a few times now is that everything builds
> locally on my pc
> but team mates can't build because my local repository differs from theirs.
> For example, I am working on 2 different projects A & B,
> each with it's own internal remote repo.
> The internal repo of A contains the ejb3 jar,
> but the other repo (the one of B) doesn't.
> When I created an indirect dependency on the ejb3 jar
> in the B project, it works locally because I 've already downloaded it for
> the project A.
> My team mates who are only working on project B, can't build and then send me
> angry e-mails :)
> It would be very nice that "mvn verify" verified that all dependencies are
> available in on of the pom defined (+ central) remote repositories.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
