CODEWITHSUNDEEP
javamavenintellij-idea
Victor Grazi
Victor Grazi

Reputation: 16510

Which class is Maven calling?

I am looking at an internal Maven application I am building in IntelliJ (same results in Eclipse), and everything looks perfectly clean.

I run clean and compile from IntelliJ (using IntelliJ build or using IntelliJ Maven support) and everything compiles fine.

However when I run the build from the command line (mvn clean compile) I am getting build exceptions (see below).

The command line seems to be looking for a genericized parameter (to the "with" method), which we are indeed passing in correctly. However it is complaining as if we were passing in a non-generic parameter.

Obviously mvn on the command line is using a different version of the "with" method than IntelliJ.

Is there any way to ask Maven to tell me which version of a class it is using, in terms of group, artifact and version of the containing jar?

Here is the precise error

[ERROR] \dev\try-deploy-1\src\main\java\com\victor\webui\WebUserInterface.java:[147,47] 
attribute(java.lang.String,org.hamcrest.Matcher<java.lang.String>) in 
org.openqa.selenium.lift.Matchers cannot be applied to 
(java.lang.String,org.hamcrest.Matcher<java.lang.Object>)

Upvotes: 0

Views: 91

Answers (2)

Robert Beltran
Robert Beltran

Reputation: 494

In Eclipse, sorry I know you are using IntelliJ, the maven build usually does an offline build that's why it's so fast. There is a way to force it to do a clean with all the jars though and I use that when I get in a bind. It is the Update Project command and it has a box to force the update of snapshots and releases. Maybe Intellij has something like that? Also I'd verify the version you are using on command line is the same as the one IntelliJ is using (I have a few versions installed). You can check Settings in IntelliJ and

mvn -v

on the command line. Finally I'd make sure the settings.xml files you are using for command line and IntelliJ are the same file.

Good luck.

Upvotes: 1

Ryan Curry
Ryan Curry

Reputation: 11

Is it possible that you have another version of the class somewhere? try adding a comment on a new line in the file so the line number changes, and re-run the maven compile to see if it still gives the same line number for the error.

Upvotes: 1

Related Questions