Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
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.