Currently the Activiti Explorer application is packed as a Web Application (.war) but to ease the integration of the Explorer into existing Web Applications it sohuld be split up into a JAR containing the actual application and a Web Application (WAR) depending on this JAR which then includes all the configuration files necessary to run Explorer standalone. The Activiti Explorer Web-Application artifact is called activiti-webapp-explorer2. This artifact and its name could be maintained while creating a new artifact called activiti-explorer2 of package type "jar".
What should be considered as well when doing this is that the Process Engine instance to be used by the Explorer Application should be configurable. However these 2 steps could be split up into 2 seperate issues.
Are there any reasons speaking against this? For example problems arising because of the usage of Vaadin?