On 08/05/2011 14:16, Geoffrey De Smet wrote:
Looks like kris found the real cause why you didn't get the latest
mvel snapshot as needed:
https://github.com/droolsjbpm/jbpm/commit/23339ee970843066e7eaa8e625c4a096edc562a6#L1L66
I agree we should strongly prefer not to use mvel snapshot's if we can
avoid it (which we can't for this release :( ).
We'd need to do some preliminary testing agains the snapshot anyway,
before we can push a release. Otherwise you are releasing for every
single issue you find in MVEL.
Mark
Op 07-05-11 18:31, Antoine Toulme schreef:
We really only care about jBPM, and as of now, we build it against
M2. M2 was depending on mvel snapshot, so it started breaking when
new snapshots were introduced.
I am not a big believer in snapshots for coordinating complex
products like Drools with many moving pieces. I voiced this to Mark
in the past, and I need to discuss this with you when we have time.
Thanks,
Antoine
On Sat, May 7, 2011 at 08:42, Geoffrey De Smet
<ge0ffrey.s...@gmail.com <mailto:ge0ffrey.s...@gmail.com>> wrote:
Thanks Antoine :)
It's a good experiment.
Just hope it doesn't complicate things as the mvel snapshots
change API regularly and our snapshots are adjusted regularly to
cope with those API changes.
Op 07-05-11 09:10, Antoine Toulme schreef:
It is by no means going to help in any way for you to release.
This is just meant for us to be able to build and run Drools
while you guys figure out a solution.
Thanks,
Antoine
On Fri, May 6, 2011 at 23:54, Geoffrey De Smet
<ge0ffrey.s...@gmail.com <mailto:ge0ffrey.s...@gmail.com>> wrote:
This nights mvel snapshot fixes jbpm (the one from 3-MAY
doesn't afaik).
Does that release (it's not a snapshot) include those latest
changes?
Not that I 've not been tempted (or pressured from Mark) to
try to release mvel myself to move away from the snapshot,
but without tag of the source code in git, without a "yes,
this revision is ok" from Mike (the mvel lead), etc
this isn't the kind of dependency we want to include in the
final release and support for 5 to 7 years.
Op 06-05-11 20:04, Antoine Toulme schreef:
We pushed out this snapshot with a version for now:
http://www.intalio.org/public/maven2/org/mvel/mvel2/2.1/mvel2-2.1-intalio.jar
On Fri, May 6, 2011 at 03:51, Geoffrey De Smet
<ge0ffrey.s...@gmail.com <mailto:ge0ffrey.s...@gmail.com>>
wrote:
Hudson hasn't been reliable the last couple of days,
this might have something do with it as you might not
have the latest snapshots of everything.
Furthermore, the mvel snapshot has been changed from
1-MAY to 3-MAY
https://repository.jboss.org/nexus/index.html#nexus-search;gav~org.mvel~mvel2~2.1-SNAPSHOT~~
<https://repository.jboss.org/nexus/index.html#nexus-search;gav%7Eorg.mvel%7Emvel2%7E2.1-SNAPSHOT%7E%7E>
But I don't think that's it.
As soon as a new mvel release is out, I 'll switch us
to it. We can't use the current latest mvel release.
Op 06-05-11 12:20, Leonardo Gomes schreef:
I will try to delete mvel stuff from my repository at
home tonight to see if it fixes the problem. If not,
here's a suggestion from Antoine:
We suffered the same problem, the temporary
workaround is to use an older snapshot:
You can pick this one:
http://www.intalio.org/public/maven2/org/mvel/mvel2/2.1-SNAPSHOT/mvel2-2.1-20110328.204856-23.jar
I hope it helps.
Antoine
Leo.
On Fri, May 6, 2011 at 11:30 AM, Michael Anstis
<michael.ans...@gmail.com
<mailto:michael.ans...@gmail.com>> wrote:
I pulled, rebased just now and it's OK here.
I have deleted my mvel entries in maven recently
though, I think Wolfgang and Leo have had issues
with different versions in their local repos.
With kind regards,
Mike
On 6 May 2011 08:50, Jervis Liu <j...@redhat.com
<mailto:j...@redhat.com>> wrote:
Hi,
Looks like MVEL lib is screwed up on master.
Tried to run test scenario
Good Credit History Only, it failed with
following errors:
Unable to rebuild the rulebase.
org.drools.rule.MVELDialectRuntimeData; local
class incompatible: stream
classdesc serialVersionUID =
8808844570772337501, local class
serialVersionUID = 2609855281272796208
Jervis
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
<mailto:rules-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
<mailto:rules-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org <mailto:rules-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-dev
--
With kind regards,
Geoffrey De Smet
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
<mailto:rules-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org <mailto:rules-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-dev
--
With kind regards,
Geoffrey De Smet
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org <mailto:rules-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org <mailto:rules-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-dev
--
With kind regards,
Geoffrey De Smet
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org <mailto:rules-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
--
With kind regards,
Geoffrey De Smet
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
