| Maven project says it is missing a required project that is not a required project [message #1871019] |
Thu, 12 September 2024 18:06  |
Eclipse User |
|
|
|
I'm using the new 2024-09 release, which comes with m2e 2.6.2.20240828-1954.
I imported a project from my git repositories that I had previously imported in many previous Eclipse versions. I often have a problem with m2e (or whatever) not creating a .classpath file, but now I'm seeing a new weird problem.
The project is called "captchams", and it has numerous Maven dependencies, one of which is "idp-shutdown-jersey". The application builds perfectly fine from the mvn command line.
In Eclipse, it is saying this:
Project 'captchams' is missing required Java project: 'idp-shutdown-jersey'
In "Java Build Path" and "Projects", there are no required projects. I have "captchams" with "workspace resolution" disabled because I want it to get all artifacts from the local maven repo, not workspace projects.
I did create this issue: https://github.com/eclipse-m2e/m2e-core/issues/1829 , although the last couple of issues I've submitted to m2e were completely ignored, so I'm not really hopeful anything will come from that.
|
|
|
| Re: Maven project says it is missing a required project that is not a required project [message #1873169 is a reply to message #1871019] |
Fri, 06 December 2024 20:47  |
| Eclipse User |
|
|
|
David M. Karr wrote on Thu, 12 September 2024 22:06I'm using the new 2024-09 release, which comes with m2e 2.6.2.20240828-1954.
I imported a project from my git repositories that I had previously imported in many previous Eclipse versions. I often have a problem with m2e (or whatever) not creating a .classpath file, but now I'm seeing a new weird problem.
The project is called "captchams", and it has numerous Maven dependencies, one of which is "idp-shutdown-jersey". The application builds perfectly fine from the mvn command line.
In Eclipse, it is saying this:
Project 'captchams' is missing required Java project: 'idp-shutdown-jersey'
In "Java Build Path" and "Projects", there are no required projects. I have "captchams" with "workspace resolution" disabled because I want it to get all artifacts from the local maven repo, not workspace projects.
I did create this issue: https://github.com/eclipse-m2e/m2e-core/issues/1829 , although the last couple of issues I've submitted to m2e were completely ignored, so I'm not really hopeful anything will come from that.fantasy username
It seems like the issue might be related to how Eclipse is resolving dependencies in your project. Since the project builds fine using Maven from the command line, the problem likely lies with how Eclipse's m2e plugin is interpreting your project's dependencies.
First, ensure that all your Maven dependencies are correctly downloaded to your local repository. You can do this by running mvn clean install from the command line. Next, try updating the project in Eclipse by right-clicking on the project and selecting "Maven" > "Update Project". Make sure that "Force Update of Snapshots/Releases" is checked.
If the problem persists, check if there are any workspace resolution settings or specific m2e configurations that might be affecting this particular dependency. Also, ensure that your Eclipse and m2e plugin are fully updated to rule out any bugs that might have been fixed in subsequent updates. If none of these steps work, consider manually adding the dependency to your project's build path as a temporary workaround until the issue is resolved in m2e.
|
|
|
Powered by
FUDForum. Page generated in 0.04069 seconds
Home