Idea from https://github.com/droolsjbpm/optaplanner-wb/pull/130 review:

gdesmet@redhat.com "The playground-parent's pom.xml's "packaging" type is "pom", yet that pom.xml has a side effect of building and deploying a jar too. Combine that with the fact that "packaging" defaults to "jar" and this works.

So maybe we should split up playground-parent into kie-playground-parent and kie-playground-distribution? The modules code would go into parent, but the assembly and xslt code would go into playground-distribution. optaplanner-wb would depend on distribution instead of parent."