aboutsummaryrefslogtreecommitdiffstats
path: root/adapters/mso-tenant-adapter
AgeCommit message (Collapse)AuthorFilesLines
2017-10-12Iterate over "entrySet" instead of "keySet"rama-huawei1-1/+1
Issue-id: SO-214 Change-Id: Ic402b02a82bd613b0753db1530dd76ce59c3ad08 Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
2017-10-02Prevent JAXRS LinkageErrorArthur Martella1-1/+6
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-09-26Correcting varriable nameAnkit-Huawei1-44/+48
SO-158 Change-Id: I683896e38f349d072dcc2967dee3a00f86448e4c Signed-off-by: Ankit-Huawei <ankit.kumar.sinha1@huawei.com>
2017-09-25Replaced with Diamond symbolrama-huawei1-6/+6
Change-Id: Ibc14257b814b83427ce0078f83aaf4d6b0cc38c0 Issue-Id:SO-118 Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
2017-09-12Fix for SONAR critical issuesseshukm1-0/+10
Issue-Id : SO-117 Change-Id: I57e30d9a8a2b251a57466d92c49f41e2a5943b22 Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-09-11Change the header to SOSeshu-Kumar-M8-8/+8
IssueId: SO-120 Change-Id: I59982b12d5b538b3f9765410ac26cbdde1844957 Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-08-04Failed to deploy so artifacts in nexus (again)Rob Daugherty1-6/+6
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-6/+6
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-6/+6
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-1/+17
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 dependencyxg353y4-4/+4
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-2/+2
Change-Id: Id054e7a04ce88450c3cfe108c8259c4d287681c8 Signed-off-by: ChrisC <cc697w@intl.att.com>
2017-01-31Initial OpenECOMP MSO commitChrisC17-0/+1367
Change-Id: Ia6a7574859480717402cc2f22534d9973a78fa6d Signed-off-by: ChrisC <cc697w@intl.att.com>