If it’s a new Drools architecture, I’d recommend you use 6.1 beta3. We use GIT for source
and Maven for artefacts. You an setup different maven repo’s for dev, stage and prod and
create a copy routine to move the jars between the environments (or use a tool like
On 11 May 2014, at 05:35, Branham, Jeremy [HR] <Jeremy.D.Branham(a)sprint.com> wrote:
I am planning a new Drools architecture, and looking for the best way
to migrate Drools rules through a series of environments.
Our typical SDLC involves an initial DEV environment, then migrating to one of several
TEST environments, then to an ORT environment, then finally to a PROD environment.
The question has been asked a couple times, looking through the mail archives, but I’m
curious if there have been any recent changes that could improve the development
I’ve read we could just use the import/export function, or the following two options -
Using the Rest interface
Anything else, or any best practice for this?
Jeremy D. Branham
Sprint University Performance Support
Fort Worth, TX | Tel: **DOTNET
Office: +1 (972) 405-2970| Mobile: +1 (817) 791-1627
This e-mail may contain Sprint proprietary information intended for the sole use of the
recipient(s). Any use by others is prohibited. If you are not the intended recipient,
please contact the sender and delete all copies of the message.
rules-users mailing list