Re: [jbpm-dev] [Design of JBoss jBPM] - fixed ProcessStateDbTest
for some reason, maven seems to invalidate or block all the good things from eclipse.
before, when i worked with CVS and ant, eclipse always behaved very well as you can
do that with the basic, well tested eclipse parts.
now, with svn and maven, we need plugins that are slow and crappy. and we need to
switch to the command line regularly, and then messing up the synchronization between
filesystem and eclipse.
that is a mess. i am really in doubt if maven and svn are worth that kind of
trouble... maybe it is different with intellij. do they have better svn & mvn
integration?
regards, tom.
Heiko Braun wrote:
don't worry, you'll get used to that.
On Tue, 2008-10-21 at 11:17 +0200, Tom Baeyens wrote:
> yes. in my branch it is solved. now i'm fighting with svn switch, maven
updates,
> merging and the likes to get the changes into trunk.
>
> regards, tom.
>
>
> Heiko Braun wrote:
>> On Tue, 2008-10-21 at 04:37 -0400, tom.baeyens(a)jboss.com wrote:
>>> eventually one of the obstacles in finding the problem was that the
>>> database returned a list sorted on a timestamp. in most cases that
>>> gives a precise order... unless when the multiple process instances
>>> have a start date within the same millisecond. in that case, the
>>> order becomes random.
>> does this mean you solved the problem?
>>
>> _______________________________________________
>> jbpm-dev mailing list
>> jbpm-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbpm-dev
--
regards, tom.