It's close to impossible to tell what the problem is without a test project showing the issue.
/Anders On Thu, Mar 15, 2018 at 8:44 AM, Jonathan Yom-Tov < jon.yom...@huha-analytics.com> wrote: > I'm running `mvn clean package` every time (plus I deleted the old version > of the jar form my local repo), so I don't think that's it. > > On Thu, Mar 15, 2018 at 9:14 AM, Martin Hoeller <mar...@xss.co.at> wrote: > > > Hi! > > > > On 14 Mar 2018, Jonathan Yom-Tov wrote: > > > > > I have a fairly large project which compiles to a war file. I've > upgraded > > > the jackson dependency to 2.7.3 but for some reason 2.4.3 and 2.4.0 jar > > > files are included into the war file in addition to the 2.7.3 version. > I > > > ran mvn dependency:tree to figure out the reason but the old versions > > don't > > > appear there. They also don't appear in the build log. I deleted the > old > > > versions from my local maven repo. Didn't help. Any ideas on how to > > figure > > > this out? > > > > Did you do a "mvn clean" after upgrading? > > Maybe the old JARs just didn't get purged from you build directory. > > > > hth, > > - martin > > >
