Why do I get "Project 'captchams' is missing required Java project: 'idp-shutdown-jersey'" when it has no required projects? #1829
Comments
|
I just looked in the eclipse log, and I saw some obvious issues related to m2e: |
This is caused by
Have you checked the |
|
Ok, so I can see that if I comment out the reference to the "swagger-maven-plugin", which includes that class, and then reimport, it does get past that point. However, this is exactly the same repository that I previously imported with 2024-06, which does not have that error when I import it. However, even in 2024-06, importing this repository doesn't result in a .classpath file being created at all. There is no error saying it was unable to do it, it just finishes, and there is no .classpath file. In fact, I see this same symptom in all of our SpringBoot Maven repositories, for the last couple of releases. There was a time perhaps a year or so ago, when it was still able to generated a .classpath file on import, but not anymore. I've been forced to simply keep a copy of the old .classpath file and I copy it into each project and then make changes from the project properties dialog for any variations (generated source directories, for instance). However, I tried some experiments today, and I find that if I change my pom.xml to not specify a parent pom, it is at least able to generate a .classpath file, although it needs modifications after the fact. I suppose I could import the project with the parent pom commented out, then comment it back in and fix my project properties. It's all still a big hack, however. I also tried iterating on the parent pom, by manually changing the pom file in my local maven repo. I commented out almost all of it, only leaving the groupId, artifactId, modelVersion, version, and packaging properties. That didn't make a difference. If my repository pom specifies the parent pom, it doesn't generate the .classpath file. If I comment out the parent-pom reference, it does. This is essentially two different problems, although they might be related. |
|
It is quite hard to guess from the description, so probably you can share an example that reproduce the problem? |
I'm using the new Eclipse 4.33.0 distro, which includes 2.6.2.20240828-1954 of m2e.
I'm seeing a new problem that appears to be associated with m2e. I've imported an existing project from my git repos, which I had earlier imported in my 4.32 distribution.
The project has a red bang on it, with the one error saying this:
This project definitely depends on the "idp-shutdown-jersey" artifact, as it's a transient dependency of one of our dependencies. However, I have no idea why it thinks it depends on the "idp-shutdown-jersey" PROJECT. I have "Workspace resolution" disabled in "captchams". I do have an Eclipse project for "idp-shutdown-jersey", but I want "captchams" to depend on the Maven artifact, not the Eclipse project.
When I inspect the "Java Build Path" for "captchams" and the "Projects" tab, it lists the "ModulePath" and "Classpath" headers, but there are no projects listed there.
If it isn't obvious, this application builds perfectly fine from the "mvn" command line.
I also have other similarly constructed applications that are failing with almost exactly the same error, except for different projects being "required". I did not see these errors in 2024-06 or before.
The text was updated successfully, but these errors were encountered: