3:19 a.m.
Thanks to Edson and André for the very interesting discussion on maps in
Drools. :) I suspect my follow up question got a bit buried in that thread
and probably is a separate topic anyway, so I hope you don't mind my asking
this newbie question in a new thread.
All Drools projects created in Eclipse with the Drools plugin have a Drools
library associated with them, which shows up as a Drools Library entry on
the left in both project/package explorer, and in the project properties for
the project - in the Libraries tab for the project properties' Java Build
Path.
My question is, how do you get Eclipse to recognise an updated jar in the
Drools library please? Or perhaps it should be, how do you get Drools to
recognise an update to a jar which it uses?
Edson said in the other thread that I need to update my mvel jar to 2.0.12.
I can only find 2.0.13 but no doubt that's also got the maps bugfix.
However where I'm stuck is how get the Drools projects to use the updated
jar. I've copied the 2.0.13 jar to the Drools runtime folder on my computer
(both top level and subfolder). I've tried to add the 2.0.13 jar to the Java
build path for the project as an external jar. I've tried to create a fresh
Drools project in Eclipse. I've restarted Eclipse with -clean. The map issue
is still there, and the Drools library for the Drools projects still don't
even show 2.0.13 in the list of jars - just 2.0.10. I'm sure the crux of it
is that somewhere Drools has been told to use 2.0.10, and I don't know how
to tell it otherwise.
I'm sure it's a really easy thing to do if you know how, but I've tried
everything I can think of and am totally at a loss as to what to try next.
(Probably try to rename 2.0.13 to 2.0.10, delete or rename the old 2.0.10
and restart Eclipse?).
Would some kind person be able to point me in the right direction please?
I'm trying to think of a workaround for my project that doesn't use maps,
but ideally maps would be the best way. I'm willing to offer a box of
chocolates or a bottle of wine or beer whatever your poison of choice, if
blatant bribes will help! :D
Many thanks. Any suggestions at all would be most appreciated.
--
View this message in context:
http://www.nabble.com/Drools-library---updating-Drools-jar-tp25057905p250...
Sent from the drools - user mailing list archive at Nabble.com.
8:44 a.m.
I am no Eclipse expert, but:
"The correct way" (TM): checkout the source code, change the pom.xml to use
the correct MVEL version, rebuild the plugin and re-install. When we release
the next version, just update it.
"The easy way" (TM): add the new mvel jar to your eclipse project classpath
and move it up to be before the drools library in the eclipse project
classpath order. You will have both in the classpath, but being first in the
classpath order will make eclipse use it.
You must use 2.0.12 or 2.0.14-SNAPSHOT. When I tested 2.0.13 there was a
regression, if I remember correctly.
[]s
Edson
2009/8/20 KDR <dr.soprano(a)neverbox.com>
Thanks to Edson and André for the very interesting discussion on maps in
Drools. :) I suspect my follow up question got a bit buried in that thread
and probably is a separate topic anyway, so I hope you don't mind my asking
this newbie question in a new thread.
All Drools projects created in Eclipse with the Drools plugin have a Drools
library associated with them, which shows up as a Drools Library entry on
the left in both project/package explorer, and in the project properties
for
the project - in the Libraries tab for the project properties' Java Build
Path.
My question is, how do you get Eclipse to recognise an updated jar in the
Drools library please? Or perhaps it should be, how do you get Drools to
recognise an update to a jar which it uses?
Edson said in the other thread that I need to update my mvel jar to 2.0.12.
I can only find 2.0.13 but no doubt that's also got the maps bugfix.
However where I'm stuck is how get the Drools projects to use the updated
jar. I've copied the 2.0.13 jar to the Drools runtime folder on my computer
(both top level and subfolder). I've tried to add the 2.0.13 jar to the
Java
build path for the project as an external jar. I've tried to create a fresh
Drools project in Eclipse. I've restarted Eclipse with -clean. The map
issue
is still there, and the Drools library for the Drools projects still don't
even show 2.0.13 in the list of jars - just 2.0.10. I'm sure the crux of it
is that somewhere Drools has been told to use 2.0.10, and I don't know how
to tell it otherwise.
I'm sure it's a really easy thing to do if you know how, but I've tried
everything I can think of and am totally at a loss as to what to try next.
(Probably try to rename 2.0.13 to 2.0.10, delete or rename the old 2.0.10
and restart Eclipse?).
Would some kind person be able to point me in the right direction please?
I'm trying to think of a workaround for my project that doesn't use maps,
but ideally maps would be the best way. I'm willing to offer a box of
chocolates or a bottle of wine or beer whatever your poison of choice, if
blatant bribes will help! :D
Many thanks. Any suggestions at all would be most appreciated.
--
View this message in context:
http://www.nabble.com/Drools-library---updating-Drools-jar-tp25057905p250...
Sent from the drools - user mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @ www.jboss.com
9:25 a.m.
Edson thank you very much for your suggestions.
I wonder if it didn't work because I used 2.0.13? - I did that because I
couldn't find 2.0.12 on the download page at
http://docs.codehaus.org/display/MVEL/Downloading+MVEL - as you can see from
the attached pic I did try adding that jar to the project build path, ahead
of the "standard" Drools library.
I'll download 2.0.14-SNAPSHOT and try it with that. Don't have the strength
to rebuild etc right now! I'll report back. Thanks again for your help, much
appreciated. :)
http://www.nabble.com/file/p25063132/drools3.png drools3.png
Edson Tirelli-3 wrote:
I am no Eclipse expert, but:
"The correct way" (TM): checkout the source code, change the pom.xml to
use
the correct MVEL version, rebuild the plugin and re-install. When we
release
the next version, just update it.
"The easy way" (TM): add the new mvel jar to your eclipse project
classpath
and move it up to be before the drools library in the eclipse project
classpath order. You will have both in the classpath, but being first in
the
classpath order will make eclipse use it.
You must use 2.0.12 or 2.0.14-SNAPSHOT. When I tested 2.0.13 there was
a
regression, if I remember correctly.
[]s
Edson
--
View this message in context:
http://www.nabble.com/Drools-library---updating-Drools-jar-tp25057905p250...
Sent from the drools - user mailing list archive at Nabble.com.
11:11 a.m.
Does not matter the order in the "libraries" tab. You need to set them in
the "Order and Export" tab.
[]s
Edson
2009/8/20 KDR <dr.soprano(a)neverbox.com>
Edson thank you very much for your suggestions.
I wonder if it didn't work because I used 2.0.13? - I did that because I
couldn't find 2.0.12 on the download page at
http://docs.codehaus.org/display/MVEL/Downloading+MVEL - as you can see
from
the attached pic I did try adding that jar to the project build path, ahead
of the "standard" Drools library.
I'll download 2.0.14-SNAPSHOT and try it with that. Don't have the strength
to rebuild etc right now! I'll report back. Thanks again for your help,
much
appreciated. :)
http://www.nabble.com/file/p25063132/drools3.png drools3.png
Edson Tirelli-3 wrote:
>
> I am no Eclipse expert, but:
>
> "The correct way" (TM): checkout the source code, change the pom.xml to
> use
> the correct MVEL version, rebuild the plugin and re-install. When we
> release
> the next version, just update it.
>
> "The easy way" (TM): add the new mvel jar to your eclipse project
> classpath
> and move it up to be before the drools library in the eclipse project
> classpath order. You will have both in the classpath, but being first in
> the
> classpath order will make eclipse use it.
>
> You must use 2.0.12 or 2.0.14-SNAPSHOT. When I tested 2.0.13 there was
> a
> regression, if I remember correctly.
>
> []s
> Edson
>
--
View this message in context:
http://www.nabble.com/Drools-library---updating-Drools-jar-tp25057905p250...
Sent from the drools - user mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @ www.jboss.com
11:16 a.m.
There's another way.....
In the Eclipse Plugin Preferences (Eclipse -> Preferences -> Drools ->
Installed Drools Runtime) you point to the location of the Drools
runtime you want to use. If you swap out the MVEL file at the location
of your Drools Runtime it should pick up the right version of the MVEL.
You could also duplicate the jar files in that folder into a "Patch"
folder, replace the MVEL jar in the PATCH copy, and setup a "Patch
Drools Runtime" if you want to keep your original installation pristine.
You will likely need/want to bounce Eclipse for this to take effect.
________________________________
From: rules-users-bounces(a)lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Edson Tirelli
Sent: Thursday, August 20, 2009 12:12 PM
To: Rules Users List
Subject: Re: [rules-users] Drools library - updating Drools jar
Does not matter the order in the "libraries" tab. You need to set
them in the "Order and Export" tab.
[]s
Edson
2009/8/20 KDR <dr.soprano(a)neverbox.com>
Edson thank you very much for your suggestions.
I wonder if it didn't work because I used 2.0.13? - I did that because I
couldn't find 2.0.12 on the download page at
http://docs.codehaus.org/display/MVEL/Downloading+MVEL - as you can see
from
the attached pic I did try adding that jar to the project build path,
ahead
of the "standard" Drools library.
I'll download 2.0.14-SNAPSHOT and try it with that. Don't have the
strength
to rebuild etc right now! I'll report back. Thanks again for your help,
much
appreciated. :)
http://www.nabble.com/file/p25063132/drools3.png drools3.png
Edson Tirelli-3 wrote:
I am no Eclipse expert, but:
"The correct way" (TM): checkout the source code, change the pom.xml
to
use
the correct MVEL version, rebuild the plugin and re-install. When we
release
the next version, just update it.
"The easy way" (TM): add the new mvel jar to your eclipse project
classpath
and move it up to be before the drools library in the eclipse project
classpath order. You will have both in the classpath, but being first
in
the
classpath order will make eclipse use it.
You must use 2.0.12 or 2.0.14-SNAPSHOT. When I tested 2.0.13 there
was
a
regression, if I remember correctly.
[]s
Edson
--
View this message in context:
http://www.nabble.com/Drools-library---updating-Drools-jar-tp25057905p25
063132.html
Sent from the drools - user mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @ www.jboss.com
11:35 a.m.
Cool, living and learning! Thanks,
Edson
2009/8/20 Pegram, Macon <zmpegram(a)choosehmc.com>
There’s another way…..
In the Eclipse Plugin Preferences (Eclipse -> Preferences -> Drools ->
Installed Drools Runtime) you point to the location of the Drools runtime
you want to use. If you swap out the MVEL file at the location of your
Drools Runtime it should pick up the right version of the MVEL.
You could also duplicate the jar files in that folder into a “Patch”
folder, replace the MVEL jar in the PATCH copy, and setup a “Patch Drools
Runtime” if you want to keep your original installation pristine.
You will likely need/want to bounce Eclipse for this to take effect.
------------------------------
*From:* rules-users-bounces(a)lists.jboss.org [mailto:
rules-users-bounces(a)lists.jboss.org] *On Behalf Of *Edson Tirelli
*Sent:* Thursday, August 20, 2009 12:12 PM
*To:* Rules Users List
*Subject:* Re: [rules-users] Drools library - updating Drools jar
Does not matter the order in the "libraries" tab. You need to set them
in the "Order and Export" tab.
[]s
Edson
2009/8/20 KDR <dr.soprano(a)neverbox.com>
Edson thank you very much for your suggestions.
I wonder if it didn't work because I used 2.0.13? - I did that because I
couldn't find 2.0.12 on the download page at
http://docs.codehaus.org/display/MVEL/Downloading+MVEL - as you can see
from
the attached pic I did try adding that jar to the project build path, ahead
of the "standard" Drools library.
I'll download 2.0.14-SNAPSHOT and try it with that. Don't have the strength
to rebuild etc right now! I'll report back. Thanks again for your help,
much
appreciated. :)
http://www.nabble.com/file/p25063132/drools3.png drools3.png
Edson Tirelli-3 wrote:
>
> I am no Eclipse expert, but:
>
> "The correct way" (TM): checkout the source code, change the pom.xml to
> use
> the correct MVEL version, rebuild the plugin and re-install. When we
> release
> the next version, just update it.
>
> "The easy way" (TM): add the new mvel jar to your eclipse project
> classpath
> and move it up to be before the drools library in the eclipse project
> classpath order. You will have both in the classpath, but being first in
> the
> classpath order will make eclipse use it.
>
> You must use 2.0.12 or 2.0.14-SNAPSHOT. When I tested 2.0.13 there was
> a
> regression, if I remember correctly.
>
> []s
> Edson
>
--
View this message in context:
http://www.nabble.com/Drools-library---updating-Drools-jar-tp25057905p250...
Sent from the drools - user mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @ www.jboss.com
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @ www.jboss.com
12:16 p.m.
New subject: Hooray! Re: Drools library - updating Drools jar
Thanks Macon and Edson. Macon I did try the swapping out in the Drools
runtime folder (i.e. removing the 2.0.10 jars and adding in the
2.0.14_snapshot), but then Eclipse completely died (errors even with the
existing rules, because they no longer were able to resolve types). I figure
that was because the plugin was still looking for 2.0.10 and wasn't happy
that only 2.0.14_snapshot was on offer.
This is what I did before trying a new runtime folder:
- Downloaded 2.0.14_snapshot and saved it into my current Drools runtime
folder (both top level and lib for luck)
- Added 2.0.14_snapshot as an external JAR to my project's Java build path
in Eclipse - it was at the top (as in the pic in one of my previous posts).
- Didn't work (even on restarting Eclipse) so I guess it didn't use
2.0.14_snapshot even tho' it was at the top of the build path list. Again,
because I think the plugin was looking for 2.0.10.
Then I did this, which worked! - I know it was probably a bit naughty of me
because I really ought to be editing the POM and rebuilding it all as Edson
suggested, but a workaround is a workaround...
- Closed Eclipse.
- Renamed the 2.0.10 to something else in top level and lib subfolders of
the Drools Runtime folder
- Renamed 2.0.14_snapshot to the 2.0.10 name in both folders
- Restarted Eclipse
- It works! To be precise, because the bug I was trying to get the fix for
was described in another thread, it is now accepts -
m: Map( this[$str] == 1 )
without any "org.drools.RuntimeDroolsException: Exception executing
predicate this[$str] == 1" - and the rule even runs as expected.
I'm waiting till tomorrow before really celebrating, just in case, but I
think that did it. If it reverts back to the old problem, I will try your
brand new runtime folder suggestion then, Macon.
Thanks again for everyone's help.
Edson Tirelli-3 wrote:
Cool, living and learning! Thanks,
Edson
2009/8/20 Pegram, Macon <zmpegram(a)choosehmc.com>
> There’s another way…..
>
>
>
> In the Eclipse Plugin Preferences (Eclipse -> Preferences -> Drools ->
> Installed Drools Runtime) you point to the location of the Drools runtime
> you want to use. If you swap out the MVEL file at the location of your
> Drools Runtime it should pick up the right version of the MVEL.
>
>
>
> You could also duplicate the jar files in that folder into a “Patch”
> folder, replace the MVEL jar in the PATCH copy, and setup a “Patch Drools
> Runtime” if you want to keep your original installation pristine.
>
>
>
> You will likely need/want to bounce Eclipse for this to take effect.
>
--
View this message in context:
http://www.nabble.com/Drools-library---updating-Drools-jar-tp25057905p250...
Sent from the drools - user mailing list archive at Nabble.com.
12:39 p.m.
New subject: Hooray! Re: Drools library - updating Drools jar
I'm glad you found a solution that works for you.
Yes.. The Eclipse Editor gets unhappy when you do the switch. You need
to use the Preferences menu to indicate that you've made a change to the
Drools Runtime, and as I suggested you will likely need to stop/restart
Eclipse.
I was able to follow the procedure I suggested earlier today and saw the
new MVEL in the Drools Library list.
Macon
-----Original Message-----
From: rules-users-bounces(a)lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On Behalf Of KDR
Sent: Thursday, August 20, 2009 1:16 PM
To: rules-users(a)lists.jboss.org
Subject: [rules-users] Hooray! Re: Drools library - updating Drools jar
Thanks Macon and Edson. Macon I did try the swapping out in the Drools
runtime folder (i.e. removing the 2.0.10 jars and adding in the
2.0.14_snapshot), but then Eclipse completely died (errors even with the
existing rules, because they no longer were able to resolve types). I
figure
that was because the plugin was still looking for 2.0.10 and wasn't
happy
that only 2.0.14_snapshot was on offer.
This is what I did before trying a new runtime folder:
- Downloaded 2.0.14_snapshot and saved it into my current Drools runtime
folder (both top level and lib for luck)
- Added 2.0.14_snapshot as an external JAR to my project's Java build
path
in Eclipse - it was at the top (as in the pic in one of my previous
posts).
- Didn't work (even on restarting Eclipse) so I guess it didn't use
2.0.14_snapshot even tho' it was at the top of the build path list.
Again,
because I think the plugin was looking for 2.0.10.
Then I did this, which worked! - I know it was probably a bit naughty of
me
because I really ought to be editing the POM and rebuilding it all as
Edson
suggested, but a workaround is a workaround...
- Closed Eclipse.
- Renamed the 2.0.10 to something else in top level and lib subfolders
of
the Drools Runtime folder
- Renamed 2.0.14_snapshot to the 2.0.10 name in both folders
- Restarted Eclipse
- It works! To be precise, because the bug I was trying to get the fix
for
was described in another thread, it is now accepts -
m: Map( this[$str] == 1 )
without any "org.drools.RuntimeDroolsException: Exception executing
predicate this[$str] == 1" - and the rule even runs as expected.
I'm waiting till tomorrow before really celebrating, just in case, but I
think that did it. If it reverts back to the old problem, I will try
your
brand new runtime folder suggestion then, Macon.
Thanks again for everyone's help.
Edson Tirelli-3 wrote:
Cool, living and learning! Thanks,
Edson
2009/8/20 Pegram, Macon <zmpegram(a)choosehmc.com>
> There's another way.....
>
>
>
> In the Eclipse Plugin Preferences (Eclipse -> Preferences -> Drools
->
> Installed Drools Runtime) you point to the location of the Drools
runtime
> you want to use. If you swap out the MVEL file at the location
of
your
> Drools Runtime it should pick up the right version of the MVEL.
>
>
>
> You could also duplicate the jar files in that folder into a "Patch"
> folder, replace the MVEL jar in the PATCH copy, and setup a "Patch
Drools
> Runtime" if you want to keep your original installation
pristine.
>
>
>
> You will likely need/want to bounce Eclipse for this to take effect.
>
--
View this message in context:
http://www.nabble.com/Drools-library---updating-Drools-jar-tp25057905p25
066246.html
Sent from the drools - user mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
6089
days inactive
6089
days old
7 comments
3 participants
participants (3)
-
Edson Tirelli -
KDR -
Pegram, Macon