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):
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?
Hi,
I'm working on a maven web application with different submodules. In the parent
pom.xml
I have thebootstrap
dependecy to the newest version:it's then used in one of my modules, let's say "module 1":
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):where wicket-bootstrap-core seems to use:
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