CODEWITHSUNDEEP
javaeclipsemavenwar
mmcrae
mmcrae

Reputation: 11

Eclipse showing proper dependencies, but mvn package produces WAR with out-dated dependencies

I'm working with a web app, called A, using maven, in eclipse, going between using m2e eclipse plugin and command line maven.

A depends on a custom library B, which is installed in the local repo. A details this dependency in its pom.xml

When I test the app in eclipse using eclipse's Tomcat, everything is fine -- the up-to-date version of B is used, and I see so in Maven dependencies folder.

But for some reason, when I go to command line and run mvn package, the resulting WAR uses out-dated version of B. I can tell because when I get it deployed to app server, its logging and functionality is broken in a specific way that was fixed in a newer version of B.

Is there any way for me to debug what's going on here? What is eclipse doing that mvn package is not including?

Project definition:

<groupId>org.com.web</groupId>
<artifactId>DocImgTransfer_Servlet</artifactId>
<packaging>war</packaging>
<version>1.0-SNAPSHOT</version>

Dependency on lib that is somehow getting old version:

<dependency>
  <groupId>DocImgTransfer</groupId>
  <artifactId>DocImgTransfer</artifactId>
  <version>1.0.0</version>
</dependency>

So really 3 questions:

  1. If it is just some issue with maven grabbing the wrong version from local repo, is there a way for me to tell Maven to double-check the dependency version it's pulling in?

  2. Will mvn clean or mvn package -U possibly help in this case at all?

  3. Is the only advice to just double-check groupId, artifactId, version in pom.xml?

Upvotes: 1

Views: 191

Answers (1)

Saifuddin Merchant
Saifuddin Merchant

Reputation: 1171

  1. If it is just some issue with maven grabbing the wrong version from local repo, is there a way for me to tell Maven to double-check the dependency version it's pulling in?

a) Is your CustomatJar-1.0.0.jar version that eclipse is referring to same as maven is picking up or is maven picking up an older version? i.e. Do you own the code for CustomatJar and are you just updating it v/s the one getting packed in war is truly an older version e.g. CustomatJar-0.0.5

i) You could tell by just unzipping the war and seeing which version is packed inside the jar.

ii) mvn dependency:dependency would tell you which dependencies maven command line thinks should be packed. more info

  1. Is the only advice to just double-check groupId, artifactId, version in pom.xml?

Could you server have got an older version of CustomatJar in say it's lib? You did double check your POM.xml already ... correct?

Upvotes: 0

Related Questions