This content has been marked as final.
Show 6 replies
-
1. Re: jbpm 4 module dependencies
heiko.braun Feb 11, 2009 4:26 AM (in response to tom.baeyens)IMO enterprise depends on jPDL. Not on PVM.
-
2. Re: jbpm 4 module dependencies
tom.baeyens Feb 11, 2009 4:33 AM (in response to tom.baeyens)right. the tests depend indeed on jpdl.
though the enterprise sources should only depend on pvm.
so i'll mark the dependency on jpdl with scope 'test'. ok ? -
3. Re: jbpm 4 module dependencies
heiko.braun Feb 11, 2009 5:01 AM (in response to tom.baeyens)As a side note: Why do we have a custom logging framework?
-
4. Re: jbpm 4 module dependencies
tom.baeyens Feb 11, 2009 5:13 AM (in response to tom.baeyens)because jboss did not handle java.util.logging properly.
-
5. Re: jbpm 4 module dependencies
tom.baeyens Feb 11, 2009 5:16 AM (in response to tom.baeyens)image is updated.
heiko, what do you think about moving task into pvm ? do you see a disadvantage ? -
6. Re: jbpm 4 module dependencies
heiko.braun Feb 11, 2009 5:24 AM (in response to tom.baeyens)It depends on what you mean with the "task" model. IMO a final task implementation would be split into the base task model (antwerp) and a concrete implementation. Whereas the first does probably belong into the PVM, but the later doesn't.