You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jonathan Yom-Tov <jo...@huha-analytics.com> on 2018/03/14 19:39:35 UTC
old version of dependencies getting included into project
hi,
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?
thanks,
Jon.
Re: old version of dependencies getting included into project
Posted by Stephen Coy <st...@resolvesw.com.au>.
I’ve seen this happen when you have WAR overlays.
All dependency management seems to go out the window when using overlays.
Steve C
> On 15 Mar 2018, at 6:39 am, Jonathan Yom-Tov <jo...@huha-analytics.com> wrote:
>
> hi,
>
> 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?
>
> thanks,
> Jon.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: old version of dependencies getting included into project
Posted by Jonathan Yom-Tov <jo...@huha-analytics.com>.
One of the jars is jackson core, I'm trying to upgrade from 2.4.3 to 2.7.3.
It looks like the coordinates are identical.
I tried upgrading the war plugin to 3.2.0, but that didn't help.
On Thu, Mar 15, 2018 at 9:07 AM, Anders Hammar <an...@hammar.net> wrote:
> Could it be that it's a different groupId for all these jackson artifacts?
> That what explain why there are several different version for the same
> library as Maven sees it as different coordinates.
>
> I would check the jars and see if there's pom in them which would anser
> this.
> Also, I would make sure to upgrade the war plugin to the latest version. It
> could be a bug.
>
> /Anders
>
> On Thu, Mar 15, 2018 at 7:45 AM, Jonathan Yom-Tov <
> jon.yomtov@huha-analytics.com> wrote:
>
> > 100%, grep does not lie :-)
> >
> > There's also something else that's strange: as a workaround I tried to
> add
> > a packagingExcludes section to the pom.xml but the unwanted jars were
> still
> > included.
> >
> >
> >
> > On Mar 15, 2018 08:37, "Golan, Yaron" <yg...@intl.att.com> wrote:
> >
> > > Hi Jon,
> > > This scenario is very strange.
> > >
> > > Are you absolutely sure that the mvn dependency:tree didn't print it
> out?
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Jonathan Yom-Tov [mailto:jon.yomtov@huha-analytics.com]
> > > Sent: Wednesday, March 14, 2018 21:40
> > > To: users@maven.apache.org
> > > Subject: old version of dependencies getting included into project
> > >
> > > hi,
> > >
> > > 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?
> > >
> > > thanks,
> > > Jon.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> >
>
Re: old version of dependencies getting included into project
Posted by Anders Hammar <an...@hammar.net>.
Could it be that it's a different groupId for all these jackson artifacts?
That what explain why there are several different version for the same
library as Maven sees it as different coordinates.
I would check the jars and see if there's pom in them which would anser
this.
Also, I would make sure to upgrade the war plugin to the latest version. It
could be a bug.
/Anders
On Thu, Mar 15, 2018 at 7:45 AM, Jonathan Yom-Tov <
jon.yomtov@huha-analytics.com> wrote:
> 100%, grep does not lie :-)
>
> There's also something else that's strange: as a workaround I tried to add
> a packagingExcludes section to the pom.xml but the unwanted jars were still
> included.
>
>
>
> On Mar 15, 2018 08:37, "Golan, Yaron" <yg...@intl.att.com> wrote:
>
> > Hi Jon,
> > This scenario is very strange.
> >
> > Are you absolutely sure that the mvn dependency:tree didn't print it out?
> >
> >
> >
> > -----Original Message-----
> > From: Jonathan Yom-Tov [mailto:jon.yomtov@huha-analytics.com]
> > Sent: Wednesday, March 14, 2018 21:40
> > To: users@maven.apache.org
> > Subject: old version of dependencies getting included into project
> >
> > hi,
> >
> > 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?
> >
> > thanks,
> > Jon.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
RE: old version of dependencies getting included into project
Posted by Jonathan Yom-Tov <jo...@huha-analytics.com>.
100%, grep does not lie :-)
There's also something else that's strange: as a workaround I tried to add
a packagingExcludes section to the pom.xml but the unwanted jars were still
included.
On Mar 15, 2018 08:37, "Golan, Yaron" <yg...@intl.att.com> wrote:
> Hi Jon,
> This scenario is very strange.
>
> Are you absolutely sure that the mvn dependency:tree didn't print it out?
>
>
>
> -----Original Message-----
> From: Jonathan Yom-Tov [mailto:jon.yomtov@huha-analytics.com]
> Sent: Wednesday, March 14, 2018 21:40
> To: users@maven.apache.org
> Subject: old version of dependencies getting included into project
>
> hi,
>
> 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?
>
> thanks,
> Jon.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
RE: old version of dependencies getting included into project
Posted by "Golan, Yaron" <yg...@intl.att.com>.
Hi Jon,
This scenario is very strange.
Are you absolutely sure that the mvn dependency:tree didn't print it out?
-----Original Message-----
From: Jonathan Yom-Tov [mailto:jon.yomtov@huha-analytics.com]
Sent: Wednesday, March 14, 2018 21:40
To: users@maven.apache.org
Subject: old version of dependencies getting included into project
hi,
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?
thanks,
Jon.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: old version of dependencies getting included into project
Posted by Anders Hammar <an...@hammar.net>.
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.yomtov@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 <ma...@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
> >
>
Re: old version of dependencies getting included into project
Posted by Jonathan Yom-Tov <jo...@huha-analytics.com>.
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 <ma...@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
>
Re: old version of dependencies getting included into project
Posted by Martin Hoeller <ma...@xss.co.at>.
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