maven cannot find symbol class EJBClientResult

[A Kao]

My codes has these compile errors:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile (default-compile) on project proj2-war: Compilation failure: Compilation failure:
[ERROR] /C:/proj2/proj2-parent/proj2-war/src/main/java/com/mypack/web/common/MyClass.java:[220,340] cannot find symbol
[ERROR] symbol: class EJBClientResult
[ERROR] location: package mypack.ejb.myproj2

when running

  
cd C:\proj2\proj2-parent
mvn clean compile

The missing EJBClientResult class is in the mypack.common-2021.03.jar file.

Another similar project which use the same jar file compile successfully.

  
cd C:\proj1\proj1-parent
mvn clean compile

 
so the same jar file is present in my maven local repository and maven is setup properly.

To debug, run

 
mvn -X clean compile

proj1-parent output:

  
[DEBUG] com.mypack:mypack.common:jar:2021.03:compile

[DEBUG] Adding URL [file:/C:/Users/ak/.m2/repository/com/mypack/mypack.common/2021.03/mypack.common-2021.03.jar]

[DEBUG] (f) classpathElements C:\Users\ak\.m2\repository\com\mypack\mypack.common\2021.03\mypack.common-2021.03.jar

BUILD SUCCESS

 

proj2-parent output:

[DEBUG] com.mypack:mypack.common:jar:2021.03:compile

[DEBUG] (f) classpathElements C:\Users\ak\.m2\repository\com\mypack\mypack.common\2021.03\mypack.common-2021.03.jar


[ERROR] /C:/proj2/proj2-parent/proj2-war/src/main/java/com/mypack/web/common/MyClass.java:[220,340] cannot find symbol
[ERROR] symbol: class EJBClientResult
[ERROR] location: package mypack.ejb.myproj2

Both projects have the same dependency in the pom.xml:

  
    <dependency>
        <groupId>com.mypack</groupId>
        <artifactId>mypack.common</artifactId>
        <version>2021.03</version>
    </dependency>

How to fix this compile error?
Please help.
Thanks.

[Tim Holloway]

Did you do a "mvn install"?

The compile goal only compiles classes into the project's target directory. If you want to build and use a library JAR (including an EJB JAR) as a Maven dependency in another POM, you need to use the "install" goal to build the JAR and publish it to your local Maven repository.

[A Kao]

Tim Holloway wrote:Did you do a "mvn install"?

The compile goal only compiles classes into the project's target directory. If you want to build and use a library JAR (including an EJB JAR) as a Maven dependency in another POM, you need to use the "install" goal to build the JAR and publish it to your local Maven repository.

Yes, I did a "mvn install" for both projects.
Both projects used the same jar to compile, one project found it in my maven local repository but the other project did not find it.

[Tim Holloway]

In that case, I'd look at the POM for the failing project. Likely you either mis-spelled the dependency or you're referencing a version that you have not installed. Remember, Maven doesn't simply save a single instance of a JAR - it caches a separate instance for each version you install to the repository and you use that version number to ensure you got the right version for the project that depends on it.

[A Kao]

Tim Holloway wrote:In that case, I'd look at the POM for the failing project. Likely you either mis-spelled the dependency or you're referencing a version that you have not installed. Remember, Maven doesn't simply save a single instance of a JAR - it caches a separate instance for each version you install to the repository and you use that version number to ensure you got the right version for the project that depends on it.

I looked at the POM for the failing project several times.
I used Beyond Compare to compare the POM for the failing project and successful project.
They are the same.
The compile output of the failing project did not have
[DEBUG] Adding URL [file:/C:/Users/ak/.m2/repository/com/mypack/mypack.common/2021.03/mypack.common-2021.03.jar]
Is that an issue?

[Tim Holloway]

Maven does not normally list the dependencies pulled in when it compiles. In fact, I don't even know how to get it to do so.

However, the "dependency:list" goal should be able to show you what Maven should be looking for (there are IDE viewers that can also do this).