Unless the dependency specifies a version range that your lib is
outside of. But as Kalle said - start with supplying your own
dependency with desired version which should satisfy your libs'
requirements. If it does not then it's time to exclude. But be aware
that you will be overriding author's de
No need to exclude anything. The nearest resolution wins; if you
specify a different version for the same library in your pom, that's
version you are going to get.
Kalle
On Mon, Apr 5, 2010 at 11:40 AM, Thiago H. de Paula Figueiredo
wrote:
> On Mon, 05 Apr 2010 15:18:18 -0300, Everton Agner
>
On Mon, 05 Apr 2010 15:18:18 -0300, Everton Agner
wrote:
Well, has anyone upgraded the [tapestry-hibernate-5.1.0.5.jar] lib to a
newer Hibernate version via Maven?
Use the exclusion tag and provide you own Hibernate dependency. It's
documented here:
http://maven.apache.org/guides/intro
