解决 Eclipse 导入项目后 Maven Dependencies missing jar 问题
maven
Maven: Apache Maven是一个开源的项目管理和构建工具，主要用于Java项目。适合需要自动化项目构建和依赖管理的开发者。特点包括约定优于配置、易于使用和社区驱动。
项目地址：https://gitcode.com/gh_mirrors/ma/maven
免费下载资源
·
话不多说直接上图
上图是我通过git导入项目后， Maven Dependencies Library中很多包出现missing错误， 变动pom.xml文件再保存也不能自动下载缺失的包。
解决方法如下：
项目右键maven->update project。
如果还有 missing 的jar，再项目右键maven->update project，但是这次勾选 Force Update ...那一行，再OK。
如果此时依然有 missing的jar，按照 buildpath 提示的 jar包missing 路径，去 maven 本地仓库中对应位置，删掉 该 jar 包的 xxx.lastUpdated 文件，之后，再重新执行 项目右键maven->update project。
GitHub 加速计划 / ma / maven
36
2
下载
Maven: Apache Maven是一个开源的项目管理和构建工具，主要用于Java项目。适合需要自动化项目构建和依赖管理的开发者。特点包括约定优于配置、易于使用和社区驱动。
最近提交(Master分支：1 个月前 )
9b955261
This commit fixes the regression where resources with a relative targetPath
were being copied to the project root instead of relative to the output
directory (target/classes or target/test-classes).
Changes:
1. DefaultSourceRoot.fromModel: Store targetPath as a relative path instead
of resolving it against baseDir and outputDir. This ensures that
SourceRoot.targetPath() returns a relative path as intended by the
Maven 4 API javadoc.
2. ConnectedResource.computeRelativeTargetPath: Simplified to directly
return the relative targetPath from SourceRoot, since it's now always
stored as relative.
3. Updated tests to expect relative paths from SourceRoot.targetPath().
Maven 4 API Conformance:
- SourceRoot.targetPath() returns an Optional<Path> containing the explicit
target path, which should be relative to the output directory (or absolute
if explicitly specified as absolute).
- SourceRoot.targetPath(Project) resolves this relative path against the
project's output directory to produce an absolute path.
Maven 3 Compatibility:
- Resource.getTargetPath() in Maven 3 was always relative to the output
directory. This behavior is preserved by storing targetPath as relative
in SourceRoot and converting it back to relative for the Resource API
via ConnectedResource.
Example: With <targetPath>custom-dir</targetPath>:
- Maven 3: Resources copied to target/classes/custom-dir
- Maven 4 (before fix): Resources copied to project-root/custom-dir
- Maven 4 (after fix): Resources copied to target/classes/custom-dir
Fixes #11381
2 天前
83a38634
When using flatten-maven-plugin with updatePomFile=true and parent expansion,
Maven incorrectly detected a parent cycle during the install phase. The error
occurred because the consumer POM builder was using Path instead of ModelSource
when reading the flattened POM.
This change updates the PomArtifactTransformer API to use ModelSource instead
of Path. ModelSource includes the necessary context (base directory, ModelLocator)
to properly resolve parent POMs and avoid false cycle detection.
Changes:
- Updated PomArtifactTransformer.transform() to accept ModelSource instead of Path
- Modified ConsumerPomArtifactTransformer to create ModelSource with proper resolution context
- Updated DefaultConsumerPomBuilder and related classes to work with ModelSource
- Added integration test to verify the fix
Fixes #11399
(cherry picked from commit 5ec059c2d75393aaada2d2c1d0fe0100a1f79554)
3 天前
新一代开源开发者平台 GitCode，通过集成代码托管服务、代码仓库以及可信赖的开源组件库，让开发者可以在云端进行代码托管和开发。旨在为数千万中国开发者提供一个无缝且高效的云端环境，以支持学习、使用和贡献开源项目。
更多推荐
3
0- 0
已为社区贡献3条内容
所有评论(0)