aboutsummaryrefslogtreecommitdiffstats
path: root/adapters/mso-sdnc-adapter
AgeCommit message (Collapse)AuthorFilesLines
2017-09-27Merge "Fixed Blocker issues. IssueId: SO-165"Rob Daugherty2-9/+3
2017-09-27Merge "Adding comments for empty constructor"Seshu Kumar M2-0/+2
2017-09-27Fixed Blocker issues.seshukm2-9/+3
IssueId: SO-165 Change-Id: I7c2520af9394ceb600a5a25fa9acfd095d872a1d Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-09-26Correcting varriable nameAnkit-Huawei2-6/+6
SO-158 Change-Id: I683896e38f349d072dcc2967dee3a00f86448e4c Signed-off-by: Ankit-Huawei <ankit.kumar.sinha1@huawei.com>
2017-09-26Adding comments for empty constructorAnkit-Huawei2-0/+2
SO-158 Change-Id: I82c0cfc4bc642fea34480feee0d5fb0bcebffe60 Signed-off-by: Ankit-Huawei <ankit.kumar.sinha1@huawei.com>
2017-09-22Replaced with Diamond symbolrama-huawei1-4/+4
Removed useless parentheses Issue-Id:SO-118 Change-Id: I79c55aebe53e82bc649c4524e5a1029a5b7a496f Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
2017-09-22Removed useless parenthesesrama-huawei3-14/+11
Issue-Id:SO-118 Change-Id: I03173685857798cc12d5df532854a062ff08bf1c Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
2017-09-18Fixed issues in adapter packageseshukm7-31/+67
Issue-Id: SO-141 Change-Id: I1a6905aa7e1328e47b3d0f7580a1dca33c6a069c Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-09-11Change the header to SOSeshu-Kumar-M36-36/+36
IssueId: SO-120 Change-Id: I59982b12d5b538b3f9765410ac26cbdde1844957 Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-09-081710 Rebase - Second AttemptArthur Martella2-1/+7
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-5/+5
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-5/+5
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-5/+5
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-09[MSO-8] Additional fixes for the second rebaseDeterme, Sebastien (sd378r)2-5/+5
DB fixes + BPMN flows and groovy fixes + Fix issue with CloudConfig file not reloaded properly when it's wrong (JSON error or model hierarchy mistake) at MSO startup Change-Id: I2853030b78499e2a761706b643ea210955e72de3 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com> [MSO-8] Restore files removed in patch set 2 Those groovy files must be there Change-Id: I9a47ac3d9c8fc06774a1b8f518491b1b0b00af04 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-05-02[MSO-8] Second step of the rebase for MSODeterme, Sebastien (sd378r)1-1/+1
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 dependencyxg353y29-49/+2257
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>
2017-03-13Update to version 1.1.0ChrisC1-3/+3
Change-Id: Id054e7a04ce88450c3cfe108c8259c4d287681c8 Signed-off-by: ChrisC <cc697w@intl.att.com>
2017-02-06Fix FileNotFoundException in SDNC adapterDeterme, Sebastien (sd378r)1-9/+9
When SDNC returns HTTP 4XX code, there could be a FileNotFoundException that prevents the adpater to send back the answer to BPMN engine. Change-Id: I0f8ef5eaf95140a5d044e294f882412c8aaa4b53 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-01-31Initial OpenECOMP MSO commitChrisC38-0/+3489
Change-Id: Ia6a7574859480717402cc2f22534d9973a78fa6d Signed-off-by: ChrisC <cc697w@intl.att.com>