failing test for bug where jetty env content not being renamed when importing an app
replacing old app name in jetty-env.xml during import-app
preventing jetty-env.xml from being renamespaced if its part of a default aspect
adding ; as a delimeter when looking for old app name to replace when importing the app
Merge pull request #1079 from BladeRunnerJS/bugfix-jettyenv-content-not-renamed-on-import

Bugfix jettyenv content not renamed on import