AnsweredAssumed Answered

Best practice for managing version of external resources?

Question asked by dbrucegrant on Nov 11, 2014
Latest reply on Nov 20, 2014 by jbarrez
I am new to Activiti and have spent the better part of the last two weeks reading and working through the basics. I have a working development and deployment environment and have developed several simple workflows that use external resources. I have been using Activiti Explorer to deploy the workflow definitions and copying the supporting JAR file to activiti-explorer/WEB-INF/lib. When re-deploying, Activiti takes care of versioning of the workflow (and so any in-process workflows use the right version and new worflows use the latest). 

After working with deployment/re-deployment, I now realize that if the supporting business logic in the JAR file changes then I need to be able to address the issue of version there as well (so the workflow version matches the backing logic). It doesn't appear that this capability is built-in to Activiti (but please correct me if that's inaccurate - I'd be happy to be wrong :-)

My question is - what is considered best practice for managing versions of external resources?