Description of problem:

Deployment of the business-central project to the remote maven repository - via configuring distributionManagement section of pom.xml behaves differently than deployment of the equally configured project deployed via command line (mvn deploy).

This seems to be related to only -SNAPSHOTS artefacts.


Version-Release number of selected component (if applicable):

BPM 6.0.2
How reproducible:
always

Steps to Reproduce

1) Set version of business-central project to -SNAPSHOT
2) add following snippet to pom.xml

  <distributionManagement>
    <repository>
      <uniqueVersion>false</uniqueVersion>
      <id>corp1</id>
      <name>Corporate Repository</name>
      <url>file:///home/username/Downloads/myrepo</url>
      <layout>default</layout>
       <snapshots>
        <enabled>true</enabled>
      </snapshots>
    </repository>
   
    </distributionManagement>

3) deploy the project - the artefact is not deployed into the repository.
4) Change the above maven config for


<distributionManagement>
   <snapshotRepository>
      <uniqueVersion>false</uniqueVersion>
      <id>propSnap</id>
      <name>Propellors Snapshots</name>
      <url>file:///home/osiris/Downloads/myrepo</url>
      <layout>default</layout>
    </snapshotRepository>
    </distributionManagement>

build the project again. The artefact is correctly deployed. Both configuration works when executing "mvn deploy" command from command line using 3.0.5 - proof http://pastebin.test.redhat.com/227636

This is what maven documentation says: The repository elements will be used for snapshot distribution if the snapshotRepository is not defined. So this means that both configuration should work also in business-central.

Actual results:

Same maven configuration used in business-central project and in project built outside is not giving the same result.
Expected results:

Same configuration works in business-central project and also in the project built/deployed outside of business-central


Additional info: