Put your config in a and that way the war projects
need only specify
org.codehaus.mojo.jspc
jspc-maven-plugin
and they'll pick up the config from the plugin management section.
Alternatively, use two parent poms, one for the jars and the other for the wars
These need not requir
Many plugins offer a 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
true in the non-WAR children projects.
Wayne
On
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
