-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
skipPomModules/packagingSupporteds not working #128
Comments
Which maven version are you using? Is there an example that reproduces this behavior? |
Cannot reproduce. |
Sorry for the radio silence, kind of forgot about this one. I'm on Maven 3.3.3 @ OS X. That's the project where I noticed this behavior: https://github.com/hibernate/hibernate-search/blob/master/pom.xml. |
Could reproduce with Maven 3.3.3 @ Ubuntu 14.04. You defined the plugin within the |
I'd like to configure japicmp in the root POM of my multi-module Maven project. Of course, no report is needed for the root module itself. Two settings seem to be provided to help with that:
Unfortunately though, both don't take any affect, i.e. the plug-in is still run for the root module, resulting in an exception about the JAR file of that module missing (which is natural, as it has POM packaging). I took a quick look in the debugger and the
mavenProject
injected into the Mojo isnull
, resulting in an early return from the filter method.Any idea why that could be the case?
The text was updated successfully, but these errors were encountered: