PLANNER-722: Workbench: Add import example option to Project Authoring perspective #130
Conversation
| <!-- KIE Workbench Playground Repository --> | ||
| <dependency> | ||
| <groupId>org.kie.workbench.playground</groupId> | ||
| <artifactId>playground-parent</artifactId> |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Ok to merge this PR as is and threat this comment in a separate set of PR's if you agree with it.
There was a problem hiding this comment.
@ge0ffrey I agree the structure could be reworked to make things a bit more transparent. I created https://issues.jboss.org/browse/GUVNOR-2862 to fix this.
No description provided.