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):
Steps to Reproduce
1) Set version of business-central project to -SNAPSHOT
2) add following snippet to pom.xml
3) deploy the project - the artefact is not deployed into the repository.
4) Change the above maven config for
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.
Same maven configuration used in business-central project and in project built outside is not giving the same result.
Same configuration works in business-central project and also in the project built/deployed outside of business-central
My understanding is that business-central should use what's in kie-ci on that regards so I don't see how they could have a different behavior. For this reason I believe that there is some point in business-central where it is doing something custom instead of doing the deploy through kie-ci. I am reassigning this ticket to Michael so he could check this.
Verification of this BZ is blocked by BZ 1183984 - setting back to MODIFIED to verify again with ER5.
Deployment works well. Verified on ER6.