Re: AW: AW: [jbpm-dev] Published jbpm4 API
in general, we should add 'convinience' last and aim for maintainability
and manageability first. enforcing costraints on dependencies is one
of those aspects.
IMO it's an important pre-condition to actually bring jBPM4 to GA.
On Feb 3, 2009, at 3:52 PM, Heiko Braun wrote:
how we finally distribute it is another story.
but if we want compile time checking that the examples only work
against the public API
then we need separate jars. it's something tom and me talked about
in our last meeting.
On Feb 3, 2009, at 3:40 PM, Bernd Rücker wrote:
> Jbpm 3 was one jar, the people love it :-)
_______________________________________________
jbpm-dev mailing list
jbpm-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev