Andrew,
The idea is that Eclipse itself uses the runtime you specify yourself,
so when you define your Drools runtime, you point Eclipse to one
specific directory where the runtime can be found Eclipse will use that
one. Even if you update Eclipse, if you don't change the runtime, you
will still be using the same Drools classes. To update to a newer
version, create a new runtime for the newer Drools release and have the
project use that one.
In theory, you should be able to simply upgrade to the latest version of
the plugin (for all cool and new features) but still be able to execute
your rules on your selected version of the Drools runtime. If you still
have issues with your runtime, could you send me a more detailed
explanation on what you are doing exactly (like I had a 5.0.0M1 plugin
with 5.0.0M1 runtime, then updated the plugin to 5.0.0CR1 with the same
runtime, etc.)?
Thx,
Kris
Quoting Andrew Waterman <andrew.waterman(a)gmail.com>:
I upgraded from an earlier version of the Eclipse plugin (M1) to
5.0.1
earlier this week. I noticed a strange issue around the Drools
"runtime". It seems as though drools keeps a full runtime of the
version that the plugin is tied to even after being completely
uninstalled and reinstalled. There looked to be a change in the
parser between M5 and 5.0.1 (probably earlier, in the CR) that was
caught in my Maven runtime environment but not in Eclipse due to this
runtime issue.
Are there plans to upgrade these runtimes on installation/upgrade?
Should I open a JIRA on this?
best wishes,
Andrew
---------------------------------
Andrew Waterman
San Cristóbal de las Casas, Chiapas, Mexico
El 30/08/2009, a las 10:55 a.m., ekke escribió:
> I also have best experiences to use the Update Sites from
>
http://labs.jboss.com/tools/download
> because they are P2 Update Sites and you can choose between
> stable, development, nightly
>
> thx to JBoss Team to provide these sites now online
> (first sites were only download-sites)
>
> ekke
>
> Jesper S. Knudsen schrieb:
>>
>> Hi Michael
>>
>> I had som problems with Eclipse 3.5 and Drools 5.0.1 stabel. But
I
>> managed to get the Drools 5.1.0 development to work fine with
>> Eclipse 3.5
>> I just added the downloaded development version of
>> JBossTools-Update-3.1.0.M2-N200907092133-H355.zip and installed it
>> from
>> this file.
>>
>> Remember to remove the Drools version 5.0.1 from the Eclipse 3.5
>> plugins
>> and feature folders if you have tried to install it with Eclipse
3.5
>> other wise you may get som fatal errors or conflict in Eclipse
when
>> the
>> starting the environment.
>>
>> Best regrads
>>
>> Jesper S. Knudsen
>>
>>
>> J Michael Dean skrev:
>>
>>> Sorry because I am sure this has been answered, but cannot find.
>>> Compelling reasons to switch to Eclipse 3.5 because of recent
>>> changes
>>> to Mac OSX but documentation pretty clearly indicates 3.4 for
Drools
>>> 5.0. Is Drools 5.0 compatible with Eclipse 3.5?
>>>
>>> - Mike
>>> _______________________________________________
>>> rules-users mailing list
>>> rules-users(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/rules-users
>>>
>>>
>>>
>> _______________________________________________
>> rules-users mailing list
>> rules-users(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/rules-users
>>
>>
>
>
> --
> ekke (ekkehard gentz)
> independent software-architect
> senior erp-consultant
> eclipse | osgi | equinox | mdsd | oaw | emf | uml
> max-josefs-platz 30, D-83022 rosenheim, germany
> mailto:ekke@ekkes-corner.org
> homepage (de):
http://gentz-software.de
> blog (en):
http://ekkes-corner.org
> twitter: @ekkescorner
> skype: ekkes-corner
> Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID: DE189929490
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users