We were excited to update our Activiti version to the latest Activiti 5.16.4 release. In addition to the Activiti engine, we use the activiti-explorer for maintaining deployments. Because we run in a WebLogic environment, we had to pull down the source code and make a few tweeks to get activiti-explorer running. Upon going through the changes, we noticed there are a bunch of properties file changes that aren't documented changes nor are they mentioned in the 5.16.4 user guide (http://activiti.org/userguide/index.html). Is there a reason these changes aren't mentioned and is there an estimated time when the documentation will be updated to reflect the changes?
But the above reply in this post is positive towards using explorer for production purposes. Does this mean the latest version of the explorer (Vaadin based) good for production base and extension? If so, we might save time in typical setup and learning curve around best practices you have followed. Kindly advice ..
Explorer for us is not a production app. It is something we use as testing ground and its fully open source. If people deem it good enough for production, sure no problem with using it in production.
However, keep in mind we are using it to showcase features, and it has very little qa and no support. But as with everything open source, you can simply take the code, enhance it and do as you please!