Different version for different application modules

[mat-ale]

Hi,

I'm working on a maven web application with different submodules.
In the parent pom.xml I have the bootstrap dependecy to the newest version:

<dependency>
  <groupId>org.webjars</groupId>
  <artifactId>bootstrap</artifactId>
  <version>4.1.3</version>
</dependency>

it's then used in one of my modules, let's say "module 1":

<dependency>
  <groupId>org.webjars</groupId>
  <artifactId>bootstrap</artifactId>
</dependency>

There is a second module (let's say "module 2") that uses Apache Wicket and needs a dependency for Bootstrap integration.
So the following dependencies are used (still in my pom.xml file):

<dependency>
  <groupId>de.agilecoders.wicket</groupId>
  <artifactId>wicket-bootstrap-core</artifactId>
  <version>0.10.17</version>
</dependency>
<dependency>
  <groupId>de.agilecoders.wicket</groupId>
  <artifactId>wicket-bootstrap-extensions</artifactId>
  <version>0.10.17</version>
  <exclusions>
    <exclusion>
      <groupId>com.google.javascript</groupId>
      <artifactId>closure-compiler</artifactId>
    </exclusion>
    <exclusion>
      <groupId>org.webjars.bower</groupId>
      <artifactId>summernote</artifactId>
    </exclusion>
    <exclusion>
      <groupId>org.webjars</groupId>
      <artifactId>Eonasdan-bootstrap-datetimepicker</artifactId>
    </exclusion>
    <exclusion>
      <groupId>org.webjars</groupId>
      <artifactId>momentjs</artifactId>
    </exclusion>
  </exclusions>
</dependency>

where wicket-bootstrap-core seems to use:

<dependency>
  <groupId>org.webjars</groupId>
  <artifactId>bootstrap</artifactId>
</dependency>

on an old version: 3.3.7.
As result, the 2 applications (from "module 1" and "module 2") use always the latest Bootstrap version (and I just want module 1 to use it, module 2 has to still use the old version Wicket-compatible instead).

Do you think my issue is related to how the Webjars bootstrap dependency is structured now?
Any way to help me with it?

Thanks

[jamesward]

I think that is just how Maven does resolution because of how the CLASSPATH works.