You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Geoffrey De Smet (JIRA)" <ji...@codehaus.org> on 2006/06/09 15:46:27 UTC
[jira] Created: (MVERIFIER-1) Verify that all dependencies are
available in one of the remote repositories
Verify that all dependencies are available in one of the remote repositories
----------------------------------------------------------------------------
Key: MVERIFIER-1
URL: http://jira.codehaus.org/browse/MVERIFIER-1
Project: Maven 2.x Verifier Plugin
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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira