Question

When I open a POM file and click on the “Dependency Hierarchy” tab at the bottom, it gives me the error, “Project read error”. It works with other projects in the same workspace, just not with this one. Any ideas?

EDIT

In response to @Yhn’s answer.

1. Running the compile and package phases outside of Eclipse from the command-line work as expected. It compiles the application and builds the final WAR file.
2. Eclipse is indeed pointing to the default location of the Maven settings.xml file, so it should be aware of the custom repositories that are defined in it (my company has its own Maven repository).
3. I can open and edit the POM file from Eclipse, so it must have read/write permissions to the file.
4. The project is not configured in Eclipse as a Maven project, so I cannot run the package phase from Eclipse (I can only run it from the command-line).

I wonder if it has anything to do with the fact that I was having trouble building the project with Maven 3 because apparently some of the transitive dependencies are configured for Maven 1, which Maven 3 does not support (this is my theory anyway, based on some of the error messages). I can build the project with Maven 2, but I still get messages such as the following:

Downloading: http://dist.codehaus.org/mule/dependencies/maven2/org/codehaus/xfie/bcprov-jdk14/133/bcprov-jdk14-133.pom
[INFO] Unable to find resource 'org.codehaus.xfire:bcprov-jdk14:pom:133' in repsitory mule (http://dist.codehaus.org/mule/dependencies/maven2)

It must be able to find these dependences however, because it downloaded the JARs just fine and can build the application. It seems like the problem is that the dependencies don’t have POM files associated with them, which is maybe why they cannot be used with Maven 3. This might also be why I cannot view the Dependency Hierarchy in Eclipse.

EDIT 2

I converted the project to a Maven project by going to “Configure > Convert to Maven Project”. When I open the POM file, I see the error:

ArtifactDescriptorException: Failed to read artifact descriptor for woodstox:wst (Click for 140 more)

(woodstox:wst is another transitive dependency of the project). An error appears in the “Markers” view for seemingly every depedency and transitive dependency in my project. However, I can successfully build the project by doing a “Run As > Maven build”. (Edit: This might be because this project has no Java source code, but the JARs of the dependencies correctly appear in the final WAR.) The Dependency Hierarchy still gives the same error–“Project read error”.

About the “Unable to find resource” messages–but this only appears for a handful of transitive dependencies. The project has many more transitive dependencies, but these messages do not appear for them. It seems like, because the dependencies do not have POM files, that Maven tries to search for them every time the project is built. Is this normal not to have POMs??

How might I go about getting a repo manager? Is this something that would have to be installed on the company’s Maven repository or can you install it on your own workstation?

Answer 1

I had this problem with some non-maven jars that I needed to include in my maven project. I put the jars in my local repository using this maven command:

mvn install:install-file -Dfile=/test/gov.nist.xccdf-1.2.jar -DgroupId=gov.nist -DartifactId=xccdf -Dpackaging=jar -Dversion=1.2

Then I referred to them as dependencies in my pom.xml:

    <dependency>
        <groupId>gov.nist</groupId>
        <artifactId>xccdf</artifactId>
        <version>1.2</version>
        <type>jar</type>
        <scope>compile</scope>
    </dependency>

This worked fine for a while, but I must have upgraded something in eclipse, and I started getting the error you describe.

The fix is to take them out of the local repository, and redo the install-file asking maven to generate a pom for you:

mvn -DgeneratePom=true install:install-file -Dfile=/test/gov.nist.xccdf-1.2.jar -DgroupId=gov.nist -DartifactId=xccdf -Dpackaging=jar -Dversion=1.2

The command will cause a pom to be generated in the same directory (within your local repo) where the jar is placed.

In recent versions of eclipse maven support, the maven build is still done with maven 2 (if you right-click your pom.xml, choose run as mvn package for example). The dependency analysis is now done with an embedded maven 3 plugin, which doesn’t like a dependency that has no pom.xml.