Justin Edelson wrote:
One thing to look at is to confirm that you are *only* specifying the plugin
versions for both maven-scr-plugin and maven-bundle-plugin in the parent
POM. Maven has a bug/feature wherein it will only use one version of a given
plugin in a multi-module build, even if different versions are specified.
For example, let's say you have this structure:
P
\- A
\- B
(parent project P with submodules A and B).
A specifies version 1.0.0 of maven-xyz-plugin and B specifies version 1.1.0
of the same. When Maven is run from P, version 1.0.0 will be used for both A
and B because that is the first version to be loaded. When Maven is run from
B (or if A was commented out), version 1.1.0 would be used.
This may not be related to your issue, but when I read the line about your
"fix," this is the first thing that came to mind. Worth a quick peek at your
poms.
Justin
Hi Justin,
thanks for your hint.
So, if I specify the versions I require the whole project to use in the
"pluginManagement" section of my
parent pom P, will that be enough to avoid this
"first-version-found-is-always-used" policy (better: to use
that policy so that the version I need is picked up and used throughout
the modules)?
Or do I still have to hunt for occurrences of the dependency *and*
version in the pom files of modules
A, B, ... ?
Guido
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
