On 3/15/2011 5:39 PM, Benjamin Bentmann wrote:
Chris wrote:
The third party jar that it's looking for does not exist in maven
central; it's a proprietary app. But it does exist in the proper place
in my local repo, with the right version number and everything (I've
triple checked).
[...]
My settings.xml is empty, if that's relevant.
Could be
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository
Thank you. That was the problem. I had had a setting.xml that pointed to
an internal repo at my company, and then cleared it out. Maven puts a
file named _maven.repositories in with the jar file in the local repo
that keeps track of where the jar came from. If the remote repo isn't
available, the build fails. Deleting _maven.repositories solved the problem.
This seems like an extrordinarily bad design. If a remote system goes
down, you can't do a build? If you have an internal repo at work, and
you take your laptop home, you can't do a build?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
