<div dir="ltr"><div>I'm easy with "W" instead of "D". How about "Integrated Work Studio" instead of "Environment"?<br><br></div><div>Group IDs proposed to be: org.drools.iws (all things drools specific) and org.kie.guvnor (generic management/workflow stuff)...<br>
<br></div><div>kie-ide would become kie-iws; and presumably jBPM modules should ideally adopt something like org.jbpm.iws (if we're to be consistent). This won't affect Guvnor's split but is something to consider.<br>
</div><div><br></div><div>I'll hold off on the split so people have time to digest the recommendation..<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 2 April 2013 09:33, Mark Proctor <span dir="ltr"><<a href="mailto:mproctor@codehaus.org" target="_blank">mproctor@codehaus.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">IWE vs IDE.<div><br></div><div>The new web framework can be a console, a workbench, an IDE, or "work" area. </div>
<div><br></div><div>We can't use the words suite or platform - as that confuses with RHT product names. So we were thinking of just using KIE IDE, as a generic work to refer to all of them - but i think "development" in the IDE might confuse people, especially where it's being used for tasks lists. So what about IWE, Integrated Work Environment. As a more generic version of IDE.</div>
<div><br></div><div>So instead of kie-ide as the base, we'd call it kie-iwe as the base.</div><span class="HOEnZb"><font color="#888888"><div><br></div></font></span><div><span class="HOEnZb"><font color="#888888">Mark</font></span><div>
<div class="h5"><br><div><div>On 28 Mar 2013, at 06:40, Toni Rikkola <<a href="mailto:toni.rikkola@gmail.com" target="_blank">toni.rikkola@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div style="word-wrap:break-word">
Yep, that looks good.<div><br></div><div>Toni</div><div><br><div><div><div>On Mar 27, 2013, at 3:33 PM, Michael Anstis wrote:</div><br><blockquote type="cite">I've put together this: <a href="https://docs.google.com/drawings/d/1zovHiCJu0TnlKDuSq4xvRcuhThiR7G3ZdOWobooerdc/edit" target="_blank">https://docs.google.com/drawings/d/1zovHiCJu0TnlKDuSq4xvRcuhThiR7G3ZdOWobooerdc/edit</a> showing my perceptions.<br>
<br>Please take a few minutes to look and feedback... I'll be checking GAVs (and the split) with Mark before making the changes...<br><br><div class="gmail_quote">On 26 March 2013 11:35, Toni Rikkola <span dir="ltr"><<a href="mailto:toni.rikkola@gmail.com" target="_blank">toni.rikkola@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>I propose that we add one more layer between drools-ide and guvnor. Name could be guvnor-kie-ide or kie-ide-guvnor.</div>
<div><br></div><div>1. Generic Guvnor</div><div>2. Kie-family modules shared between layer #3</div><div>3. Drools (drools-ide) / jBPM / OptaPlanner</div><div><br></div><div>For example the build services we have in guvnor-project will most likely be used by jBPM Guvnor , Drools Guvnor and OptaPlanner Guvnor. A clear separation between the layers would help us to keep circular dependencies away and make the code cleaner.</div>
<div><br></div><div> Toni</div><br><div><div><div><div>On Mar 26, 2013, at 12:36 PM, Michael Anstis wrote:</div><br></div></div><blockquote type="cite"><div><div>Hi,<br><br>The time to split Guvnor into "Guvnor" (common asset management/generic project framework) and "Drools IDE" (Editors for Drools assets) has arrived.<br>
<br>This is a list of the current Guvnor modules and a proposal as to the split. Please feedback any comments - I'd like to split next week (and perform related GAV changes):-<br>
<br><b>guvnor-commons<br></b><ol><li>guvnor-comons-builder ---> drools-ide</li><li>guvnor-commons-data ---> split applicable components into guvnor and drools-ide(sub-package "tables" is guvnor; the remainder are drools-ide).<br>
</li><li>guvnor-commons-security ---> drools-ide</li><li>guvnor-commons-security-api ---> drools-ide</li><li>guvnor-commons-ui ---> split applicable components into guvnor and drools-ide (some classes in sub-package "widgets" are drools-ide and sub-package "workitems" is drools-ide but can be deleted).</li>
</ol><br><b>guvnor-core</b><br><ol><li><span style="color:rgb(51,102,255)">guvnor-core-services ---> guvnor</span></li><li>guvnor-datamodel ---> drools-ide</li><li>guvnor-project ---> drools-ide</li><li><span style="color:rgb(255,0,0)">guvnor-workingsets ---> delete (not used)</span></li>
</ol><b><br>guvnor-editors<br></b><ol><li>guvnor-categories-editor ---> drools-ide</li><li>guvnor-default-editor ---> drools-ide</li><li>guvnor-drl-text-editor ---> drools-ide</li><li>guvnor-dsl-text-edutor ---> drools-ide</li>
<li>guvnor-dtable-xls-editor ---> drools-ide</li><li>guvnor-enum-editor ---> drools-ide</li><li><span style="color:rgb(51,102,255)">guvnor-explorer ---> guvnor</span></li><li>guvnor-factmodel-editor ---> drools-ide</li>
<li>guvnor-globals-editor ---> drools-ide</li><li>guvnor-guided-dtable-editor ---> drools-ide</li><li>guvnor-guided-rule-editor ---> drools-ide</li><li>guvnor-guided-scorecard-editor ---> drools-ide</li><li>
guvnor-guided-template-editor ---> drools-ide</li><li><span style="color:rgb(51,102,255)">guvnor-inbox ---> guvnor</span></li><li><span style="color:rgb(51,102,255)">guvnor-m2repo-editor ---> guvnor</span></li>
<li>guvnor-project-config-editor ---> drools-ide</li><li>guvnor-project-editor ---> drools-ide</li><li>guvnor-scorecard-xls-editor ---> drools-ide</li><li><span style="color:rgb(51,102,255)">guvnor-search-screen ---> guvnor</span></li>
<li>guvnor-test-scenario-editor ---> drools-ide</li></ol>Worthy of mention is that the "Project Editor" becomes a Drools specific
project editor (as it needs to handle both pom.xml and kmodule.xml). There is no "Project Editor" out of the box for Guvnor.<br>
<br><br><b>guvnor-webapp<br></b><ol><li>guvnor-showcase ---> drools-ide</li></ol><br><b>guvnor-widgets</b><br><ol><li>guvnor-config-resource-widget ---> drools-ide</li><li>guvnor-decorated-grid-widget ---> drools-ide</li>
<li><span style="color:rgb(255,0,0)">guvnor-error-messages-widget ---> delete (not used)</span></li><li><span style="color:rgb(51,102,255)">guvnor-metadata-widget ---> guvnor</span></li><li>guvnor-view-source-widget ---> drools-ide</li>
</ol><br><b>GAV changes<br></b><br>drools-ide components would adopt the "org.drools.ide" GroupId; guvnor components would adopt the "org.kie.guvnor" GroupId.<br><br>Package names would be corrected to follow the GAV-package naming convention.<br>
<br>With kind regards,<br><br>Mike<br></div></div>
_______________________________________________<br>rules-dev mailing list<br><a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a></blockquote>
</div><br></div><br>_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br></blockquote></div><br>
_______________________________________________<br>rules-dev mailing list<br><a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a></blockquote>
</div><br></div></div></div>_______________________________________________<br>rules-dev mailing list<br><a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a></blockquote>
</div><br></div></div></div></div><br>_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br></blockquote></div><br></div>