summaryrefslogtreecommitdiffstats
path: root/bpmn/MSOInfrastructureBPMN/pom.xml
AgeCommit message (Collapse)AuthorFilesLines
2017-11-16Remove unused dependency on dmaapClientRob Daugherty1-13/+1
A prior change created our own dmaap client, so we don't need the one provided by com.att.nsa. That one included the dme2 jar, which was causing classloading conflicts. Issue: SO-208 Change-Id: Ia0af70c060044d7c10b1ad9ba8ed2bf8385dd0a4 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-11-16changed artifact versionseshukm1-1/+1
IssueId: SO-346 Change-Id: I4bd910032baa26c2aa154d3860bf4d34ecf7d9dd Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-11-09Move unit test mocks to test scoped jarRob Daugherty1-7/+0
This commit removes the MSOMockServer artifact. The mocks are now in a test-scoped jar in MSOCommon. Issue: SO-314 Change-Id: Ifbc508c12a56cda329320adf1945c93f31ebe13c Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-11-03Fix for the snapshot solution for the MSBseshukm1-1/+1
IssueId: SO-286 Change-Id: Id43450e148dff31389a82c5a0e3695a9bb5028d7 Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-10-02Prevent JAXRS LinkageErrorArthur Martella1-0/+18
Pruning the inclusions in modules to prevent linkage errors during health check. Change-Id: I7b3cb233d0eac2a0a41b15e608d3d295a73573e7 Issue-ID: SO-160 Signed-off-by: Arthur Martella <amartell@research.att.com>
2017-10-02Fixes for Infrastructure module startupArthur Martella1-0/+6
Excluding jersey-all from pom.xml and fixing broken bpmn file. Change-Id: I466a593f08d20f6b37e367f3ccc67bd8a7165029 Issue-ID: SO-160 Signed-off-by: Arthur Martella <amartell@research.att.com>
2017-09-30remove odl dependence temporary黄卓垚101122151-2/+2
Change-Id: I2d4348974badf6b4ecb255adb3ffa3b5c399d7e2 Issue-ID: SO-88 Signed-off-by: Zhuoyao Huang <10112215@zte.com.cn> description: Remove odl dependence temporary for docker deployment, utill the issue is be solved. Before that time, yang decoder is unavailable.
2017-09-23fix a bug and ...Zhuoyao Huang1-2/+2
Change-Id: Id5dfae04cffa98705a5d99f9cf7d7552de5b8418 Issue-ID: SO-88 Signed-off-by: Zhuoyao Huang <10112215@zte.com.cn> Discription: fix a bug and commit underlay vpn achieved by yang decoder
2017-09-22underlay vpnZhuoyao Huang1-0/+19
Change-Id: I3eafc44ca701f02921dfe14a2714948cd1c21c2d Issue-ID: SO-88 Signed-off-by: Zhuoyao Huang <10112215@zte.com.cn>
2017-09-081710 Rebase - Second AttemptArthur Martella1-13/+34
This commit rebases changes from openecomp-mso/internal-staging-1710 up to and including this codecloud commit: 54483fc6606ddb1591a2e9da61bff8712325f924 Wed Sep 6 18:12:56 2017 -0400 Rebasing was done on a branch on top of this commit in so/master in ONAP: 93fbdfbe46104f8859d4754040f979cb7997c157 Thu Sep 7 16:42:59 2017 +0000 Change-Id: I4ad9abf40da32bf5bdca43e868b8fa2dbcd9dc59 Issue-id: SO-107 Signed-off-by: Arthur Martella <amartell@research.att.com>
2017-08-04Failed to deploy so artifacts in nexus (again)Rob Daugherty1-7/+7
There are Linux Foundation rules (enforced by nexus) that I still don't really understand. I'm convinced this is absolutely true: The groupId of every artifact in a project MUST begin with: org.openecomp.<project> --or-- org.onap.<project> The top-level artifact is no exception. So for example, this is NOT allowed: <groupId>org.openecomp</groupId> <artifactId>so</groupId> Here's what I'm trying now. The top level pom will contain: <groupId>org.openecomp.so</groupId> <artifactId>so-parent</artifactId> Child modules will contain: <parent> <groupId>org.openecomp.so</groupId> <artifactId>so-parent</artifactId> <version>1.1.0-SNAPSHOT</version> </parent> <groupId>org.openecomp.so</groupId> <artifactId>some-child-artifact</artifactId> Note that the groupId for the direct child module will be the same as the groupId for its parent. Issue: SO-21 Change-Id: I0d3cd2eb7a1883e23e3c0878ee7fa3dd4a7d55b2 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-08-01Failed to deploy so artifacts in nexusRob Daugherty1-7/+7
More problems encountered since mso repos were renamed. We now have found that this declaration in the top-level so pom causes the deploy to fail with a 403 Forbidden error: <groupId>org.openecomp</groupId> <artifactId>so</artifactId> We are changing this to: <groupId>org.openecomp.so</groupId> <artifactId>framework</artifactId> Issue: SO-21 Change-Id: I4e21d689c73c5071bde725127bb81482ce3d91f9 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-07-19Fix artifact group IDs (org.openecomp.so)Rob Daugherty1-7/+7
Since the repositories were renamed from "mso" to "so" the artifact group IDs in the poms must be updated to match. Issue: SO-39 Change-Id: I617fe738a77d0f6c1d1cc0ac9474fb753f4e234c Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-05-02[MSO-8] Second step of the rebase for MSODeterme, Sebastien (sd378r)1-388/+388
Second rebase containing additional features for MSO + total reworking of the BPMN structure + Notification flow can now be added at the end of some BPMN flows Change-Id: I7e937c7a0ba1593ca85e164a093f79c7e38b6ce0 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-04-11[MSO-8] Update the maven dependencyxg353y1-0/+389
Update the maven depenency for sdc-distribution-client to cooperate with the sdc changes. Change-Id: I2da936e5c40cb68c7181bb78307192dd5655b5dc Signed-off-by: xg353y <xg353y@intl.att.com>