Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>A project can have only one parent (unlike multiple inheritance in C++) but this parent can be part of a bigger parent hierarchy. As pointed out by others, you could thus have something like this:</p> <pre> base-pom/ |-- flex-base-pom | |-- my-plugin-client | | `-- pom.xml | `-- pom.xml |-- java-base-pom | |-- my-plugin-server | | `-- pom.xml | `-- pom.xml `-- pom.xml </pre> <p>That said, I noticed you wrote that your actual problem is that:</p> <blockquote> <p>flex projects inherit configuration for javadoc and pmd for example, which they do not want.</p> </blockquote> <p>You should use the <a href="http://maven.apache.org/pom.html#Plugin_Management" rel="noreferrer"><code>pluginManagement</code></a> element to avoid this situation:</p> <blockquote> <p><strong><em>pluginManagement</strong> is an element that is seen along side plugins. Plugin Management contains plugin elements in much the same way, except that rather than configuring plugin information for this particular project build, it is intended to configure project builds that inherit from this one. However, this only configures plugins that are actually referenced within the plugins element in the children. The children have every right to override pluginManagement definitions.</em></p> </blockquote> <p>So, in the parent pom, configure your plugins in <code>pluginManagement</code> (javadoc and pmd for example), and reference them within the <code>plugins</code> element in the desired children (only in my-plugin-server here). This would solve your current issue.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload