An unmanaged repository unexpectedly turned into "managed" in BRMS / BPM Suite

Environment

• Red Hat JBoss BPM Suite
  • 6.4.1

Issue

• For some reason my unmanaged repository has been turn into a managed repository. I was working in my project when I go to build it I notice I had 3 options compile, Build & Install, and Build & Deploy. I tried to build and deploy my any of my projects and I was unable. I added the role kiemgmt to my user and I notice that there is a task saying Maven Deploy Failure for every project I want to deploy. All projects which I had were unmanaged and I was able to build

Resolution

Firstly, please take a look at "Root Cause" and "Diagnostic Steps" section and check if a parent pom.xml exists in your repository. If yes, please follow the steps to change the repository back to unmanaged repository.

1. Stop BRMS
2. Backup ".niogit" directory
   3.)Edit git repositories like this:

in a working directory,

$ git clone file:///{BRMS_HOME}/bin/.niogit/system.git
$ cd system/
$ Edit {REPOSITORY_NAME}.repository "managed" entry from 'true' to 'false'

    ...
    <entry>
      <string>managed</string>
      <item>
        <name>managed</name>
        <value class="boolean">false</value>
      </item>
    </entry>

$ git commit -am 'change managed to false'
$ git push
$ git push --delete origin {username}-uf-user

$ cd ..
$ git clone file:///{BRMS_HOME}/bin/.niogit/{REPOSITORY_NAME}.git
$ cd {REPOSITORY_NAME}/
$ rm pom.xml
$ git commit -am 'remove parent pom'
$ git push

4. Start BRMS

Please note that you shouldn't push a parent pom.xml. It will turn the repo to "managed" again. So I recommend to remove it from your local development environment as well (or add /pom.xml to .gitignore).

Root Cause

There are 3 factors related to "managed".

1. user.nav and last.user.nav of -uf-user branch in system.git

        ...
        <entry>
          <string>managed</string>
          <boolean>true</boolean>
        </entry>

This directly affects the ProjectExplorer view.

2. {REPOSITORY_NAME}.repository of master branch in system.git

    ...
    <entry>
      <string>managed</string>
      <item>
        <name>managed</name>
        <value class="boolean">true</value>
      </item>
    </entry>

This is the essential information of the repository.

3. pom.xml of master branch in {REPOSITORY_NAME}.git

If there is a pom.xml directly under the repository directory (not under project directories). This pom.xml is considered as a "parent pom.xml". If a "parent pom.xml" exists, BPMS automatically converts the repository to "managed".

If you face such a situation "my unmanaged repository has been turn into a managed repository", it's likely because you pushed a parent pom.xml from local to the repository.

Diagnostic Steps

• Clone the repository to local filesystem and check if pom.xml exists directly under the repository directory (not under project directories).

git clone file://{BRMS_HOME}/bin/.niogit/{REPOSITORY_NAME}.git

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.