Hi Jonny.
We had a presentation about versioning at the community day in prague (http://blog.camunda.org/2013/10/what-wonderful-community-day-in-prague.html), see http://de.slideshare.net/camunda/community-day-2013-consulting-talks-about-camunda-bpm-best-practices (slide 15ff). There you find the basic answer – but maybe hard to see without the slides.
Quick recap:
1.) Easiest: Don’t change the forms or keep forms backwards compatible if you change them.
2.) If (and only IF) you change forms in a not backwards compatible way you can apply a simple naming convention / folder structure to avoid deploying multiple war’s
3.) You can deploy versioned WAR files – technically that works perfectly on our platform – but you have to make sure to do some stuff around “registering Process Applications at the shared engine” right. But overall this solution adds quite some complexity – so I recommend to avoid it until you have really good reasons to do so.
Cheers
Bernd
Consultant & Evangelist
--
You received this message because you are subscribed to the Google Groups "camunda BPM platform contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to camunda-bpm-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/camunda-bpm-dev/045e79c1-75ab-4bb1-862d-e550acd1b7ce%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
P.S: Added https://app.camunda.com/jira/browse/CAM-1482
To view this discussion on the web visit https://groups.google.com/d/msgid/camunda-bpm-dev/a3f5cf6c.00000838.0000004b%40ca-ruecker.