Description of problem:
From Mike Antis in email:
I had a look at the code that handled deployment to
<distributionManagement> remote repositories.
At the moment it only parses the immediate <distributionManagement>
section in the KJARs pom.xml (i.e. it does not scan parents upwards).
From Justin Holmes:
Many Customers manage distribution management as a central parent pom that each project inherits. We need to add support for this configuration.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add <distributionManagement> to a parent pom
2. Create a KIE-WB project with parent from step 1. Do not add <distributionManagement> to the KIE-WB project
3. Build and deploy
No artifacts are deployed to <distributionManagement> repositories
Artifacts should be deployed to <distributionManagement> repositories
Verified with 'file://<local-file-system-path>' repository URL. The child project deployed to repository defined in parent's <distributionManagement> after clicking Build&Deploy.