The new "Settings" UI in the workbench no longer allows me to edit the actual source of the "pom.xml" file. I get that from a "business analyst" perspective, but from a power user perspective, this is really limiting the product.

Example, I've just imported a project that I used in BPM Suite 6.4 and that I use in OpenShift S2I builds. In my POMs, I've used properties to define versions, like this:

<properties>
   <version.org.kie>7.6.0.Final-redhat-2</version.org.kie>
</properties>

<dependency>
   <groupId>org.kie</groupId>
   <artifactId>kie-api</artifactId>
   <version>${version.org.kie}</version>
   <scope>provided</scope>
</dependency>

In v6, I was able to dive directly into the POM source and edit the version in the XML file. In v7, I have a dependency-view that shows me the version of my dependency as "${version.org.kie}", but not the properties. And there seems to be no way to properly get to the source perspective for those files to edit them manually.

I understand we want to target business users, but this limitation requires power users to go through unnecessary steps of cloning the repo locally, editing the files, committing and pushing back to BC.