Put your config in a pluginManagement and that way the war projects
need only specify
plugin
groupIdorg.codehaus.mojo.jspc/groupId
artifactIdjspc-maven-plugin/artifactId
/plugin
and they'll pick up the config from the plugin management section.
Alternatively, use two parent poms,
Hi
I have a super-parent POM that all of my projects inherit...
90% of the projects are WAR files and few are multi module JARs
I would like to define a JSPC compile plugin at the super-parent POM level but
the problem arises when building non-WAR projects
How can I redefine specific
Many plugins offer a skip configuration option. Check the plugin
docs to see if jspc-m-p does, and if it does not, file a JIRA to
request that someone else add it or do it yourself. Then you could
simply add the plugin in the parent, and declare it with
skiptrue/skip in the non-WAR children
