Herko ter Horst wrote:
I think that this is a known problem of m2 - and I don't see a good
solution for this. Using different versions of plugins in different
modules makes sense as we have different release cycles (well at least
that's the plan). So the only working solution right now seems to be
to build module by module separately.
I was about to suggest using the parent pom to specify the plugin
version, but I see this is already done... although the
maven-bundle-plugin is commented out right now.
Any idea why?
To avoid circular dependencies and to be able to use a newer version of
the bundleplugin in the modules without always releasing the parent pom.
While it seems to be a nice idea to put all versions into the parent
pom, I'm coming more and more to the opinion that this is a bad idea if
your project consists of several modules that are released independently
from each other.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
