<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
The github url has been renamed.<br>
I 'll send a mail as soon as the directories and artifactId's have
been renamed<br>
together with instructions how to deal with these changes if you
prefer not to nuke your drools-planner dir.<br>
<br>
<div class="moz-cite-prefix">Op 02-03-13 14:11, Geoffrey De Smet
schreef:<br>
</div>
<blockquote cite="mid:kgstpo$6p4$1@ger.gmane.org" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Typo: this Tuesday 5-MAR (there is no this Tuesday 2-MAR :)<br>
<br>
<div class="moz-cite-prefix">Op 01-03-13 21:31, Geoffrey De Smet
schreef:<br>
</div>
<blockquote cite="mid:kgr37i$isu$1@ger.gmane.org" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hi guys,<br>
<br>
This Tuesday (2-MAR-2013), a few technical changes will occur
due to Drools Planner's namechange.<br>
<br>
1) The github URL for Drools Planner will change from <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/droolsjbpm/drools-planner">https://github.com/droolsjbpm/drools-planner</a><br>
to<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/droolsjbpm/optaplanner">https://github.com/droolsjbpm/optaplanner</a><br>
<br>
2) The groupId's and artifactId's will change from<br>
org.drools.planner:drools-planner-*<br>
to<br>
org.optaplanner:optaplanner-*<br>
<br>
3) The directory names will change accordingly.<br>
<br>
<b>If you have a clone/fork of the Drools Planner repository
with changes,</b><b><br>
</b><b>it's best to send in any changes in a pull request for
master by Monday evening</b><b><br>
</b><b>if you want to avoid a having to port those changes
manually.</b><br>
<br>
<br>
This namechange is the technical preparation for the more public
announcement we'll make in a few weeks.<br>
To avoid speculation, you can read about the full explanation of
the rename to OptaPlanner below.<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/droolsjbpm/optaplanner-website/blob/master/community/DroolsPlannerRenamed.md">https://github.com/droolsjbpm/optaplanner-website/blob/master/community/DroolsPlannerRenamed.md</a><br>
<br>
With kind regards,<br>
Geoffrey De Smet<br>
<br>
<h1>Drools Planner renamed to OptaPlanner</h1>
<p>As of version <code>6.0.0.Beta1</code>, <strong>Drools
Planner has been renamed to OptaPlanner</strong>.</p>
<h2> Why change the name?</h2>
<p>OptaPlanner is the new name for Drools Planner. OptaPlanner
is now standalone, but can still be optionally combined with
the Drools rule engine for a powerful declarative approach to
planning optimization.</p>
<ul>
<li>
<p>OptaPlanner has graduated from the <a
moz-do-not-send="true"
href="http://www.jboss.org/drools">Drools</a> project to
become a top-level <a moz-do-not-send="true"
href="http://www.jboss.org/">JBoss Community</a>
project.</p>
<ul>
<li>OptaPlanner (the planning engine) joins its siblings
Drools (the rule engine) and jBPM (the workflow engine)
in the KIE group.</li>
</ul>
</li>
<li>
<p>Our commitment to Drools hasn't changed.</p>
<ul>
<li>The efficient Drools rule engine is still the
recommended way to do score calculation.</li>
<li>Alternative score calculation options, such as pure
Java calculation (no Drools), also remain fully
supported.</li>
</ul>
</li>
</ul>
<h2> How will this affect your business?</h2>
<p>From a business point of view, there's <strong>little or no
change</strong>:</p>
<ul>
<li>
<p>The mission remains unchanged:</p>
<ul>
<li>We're still 100% committed to put <em>business
resource optimization</em> in the hands of normal Java
developers.</li>
</ul>
</li>
<li>
<p>The license remains unchanged (Apache Software License
2.0). It's still the same open source license.</p>
</li>
<li>
<p>Red Hat is considering support subscriptions offerings
for OptaPlanner as part of its <a moz-do-not-send="true"
href="http://www.redhat.com/products/jbossenterprisemiddleware/business-rules/">BRMS</a>
and BPM platforms.</p>
<ul>
<li>A <em>Tech Preview</em> of OptaPlanner is targeted
for BRMS 6.0.</li>
</ul>
</li>
</ul>
<h2> What has changed?</h2>
<ul>
<li>
<p>The website has changed to <a moz-do-not-send="true"
href="http://www.optaplanner.org">http://www.optaplanner.org</a></p>
</li>
<li>
<p>The distributions artifacts have changed name:</p>
<ul>
<li>
<p>Jar names changes:</p>
<ul>
<li> <code>drools-planner-core-*.jar</code> is now <code>optaplanner-core-*.jar</code>
</li>
<li> <code>drools-planner-benchmark-*.jar</code> is
now <code>optaplanner-benchmark-*.jar</code> </li>
</ul>
</li>
<li>
<p>Maven identification groupId's and artifactId's
changes:</p>
<ul>
<li>groupId <code>org.drools.planner</code> is now <code>org.optaplanner</code>
</li>
<li>artifactId <code>drools-planner-core</code> is
now <code>optaplanner-core</code> </li>
<li>artifactId <code>drools-planner-benchmark</code>
is now <code>optaplanner-benchmark</code> </li>
</ul>
</li>
<li>
<p>As usual, for more information see the Upgrade Recipe
in the download zip.</p>
</li>
</ul>
</li>
<li>
<p>The API's namespace has changed. As usual, see the
Upgrade Recipe on how to deal with this efficiently.</p>
<ul>
<li>Starting from 6.1.0.Final, OptaPlanner will have a
100% backwards compatible API.</li>
</ul>
</li>
<li>
<p>OptaPlanner gets its own IRC channels on <a
moz-do-not-send="true" href="http://freenode.net/">Freenode</a>:
<code>#optaplanner</code> and <code>#optaplanner-dev</code></p>
</li>
</ul>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
rules-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a></pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
rules-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a></pre>
</blockquote>
<br>
</body>
</html>