The release 6.0.0.Beta1 is done.
You will find it on Nexus.
The tagged version is on master as all originated commits.
You can commit your changes to all "masters".
During tomorrow I will upload the zips, documentation and javadocs and update the website.
Since the deploy for the release 6.0.0.Beta1 is executing now I wanted to
remind you if it is possible not to push changes on the poms until tomorrow to avoid
conflicts when merging.
I asked this in the Drools User list, but did not get a response - which
I'm looking to develop a custom UI for editing rules.
I am looking into the best way to do this. One possibility is to use the
Therefore, I would like to know if there is any documentation on
Is it possible to have a link to this?
View this message in context: http://drools.46999.n3.nabble.com/documentation-on-guvnor-webapp-core-5-5...
Sent from the Drools: Developer (committer) mailing list mailing list archive at Nabble.com.
The git repo kie-commons is currently build *before* drools.
Does that mean that drools uses code from kie-commons?
1) Which modules are depending on kie-commons's modules?
kie-commons's name is confusing to several people, including myself.
The git repo kie-commons does not contain the modules kie-api or
The modules kie-api or kie-internal are in the git repo
2) Would it make sense if we merge the git repo's droolsjbpm-knowledge
As you all must have noticed, traffic on the drools-user list has
shifted substantially from plain Expert into the Guvnor and Planner
domains. I realize that my personal balance of interests is my very
own choice. But so is the selection of mailing lists I consider worth
* Are there any plans to reorganise - split - the Drools mailing
lists in the very near future?
* Is it possible to avoid the noise resulting from git pull request
discussions from one, more or all repositories?
yes - of course
----- Ursprüngliche Mail -----
Von: "Kris Verlaenen" <kverlaen(a)redhat.com>
An: "Michael Biarnes Kiefer" <mbiarnes(a)redhat.com>
CC: jbpm-dev(a)lists.jboss.org, rules-dev(a)lists.jboss.org
Gesendet: Dienstag, 2. April 2013 18:06:27
Betreff: Re: [jbpm-dev] droolsjbpm release 6.0.0.Beta1
Could you let Edson and myself know once the release is on the staging
repo but before it is published? That allows us to do a final sanity
check before we release everything (as there's no return afterwards,
only doing a new release if we detect blocking issues).
On 04/02/2013 04:19 PM, Michael Biarnes Kiefer wrote:
> Hi all,
> I wanted to announce the new release 6.0.0.Beta1 for tomorrow, wednesday, 3rd of april 2013.
> Therefore the las commit should be done before:
> Location Local time Time zone
> Barcelona (Spain - Barcelona) wednesday,3rd april 2013, 8:00:00 CEST
> London (United Kingdom - England) wednesday,3rd april 2013, 7:00:00 BST
> New York (U.S.A. - New York) wednesday,3rd april 2013, 2:00:00 EDT
> Brussels (Belgium) wednesday,3rd april 2013, 8:00:00 CEST
> Prague (Czech Republic) wednesday,3rd april 2013, 8:00:00 CEST
> Please check if your projects compile on Jenkins.
> Thank you
> jbpm-dev mailing list
I wanted to announce the new release 6.0.0.Beta1 for tomorrow, wednesday, 3rd of april 2013.
Therefore the las commit should be done before:
Location Local time Time zone
Barcelona (Spain - Barcelona) wednesday,3rd april 2013, 8:00:00 CEST
London (United Kingdom - England) wednesday,3rd april 2013, 7:00:00 BST
New York (U.S.A. - New York) wednesday,3rd april 2013, 2:00:00 EDT
Brussels (Belgium) wednesday,3rd april 2013, 8:00:00 CEST
Prague (Czech Republic) wednesday,3rd april 2013, 8:00:00 CEST
Please check if your projects compile on Jenkins.
I opened a discussion in OSGi dev list to get some feedbacks about the
use of DI (Blueprint, CDI, Google) and DS. I got some interested notes
I'm in favor of having Drools and DS + Services, too...
Btw, have you investigated about the services to be exposed bye KIE and
I saw a lot of "*service" interfaces in new code. But I guess only a few
of them are for external uses. Could you point us which interfaces are
intent to be used by an external api? thanks.