Workaround to maven's "Failed to resolve artifact" in non-trivial dependencies

When building an old project, sometimes I encounter the dreaded Failed to resolve artifact error. What I do then is search for the jar and pom of that specific artifact and use the [mvn install:install-file goal to manually install it locally][1]. This solves the trivial case, but sometimes the project's dependency on the artifact is not trivial and includes in the project's pom fields such as: runtime or worse: cglib cglib-nodep How would you handle these cases? Is there a way to add these fields to the command as well? [1]:

以上就是Workaround to maven's "Failed to resolve artifact" in non-trivial dependencies的详细内容,更多请关注web前端其它相关文章!

赞(0) 打赏
未经允许不得转载:web前端首页 » JavaScript 答疑

评论 抢沙发

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址

前端开发相关广告投放 更专业 更精准