summaryrefslogtreecommitdiffstats
path: root/asdc-controller/pom.xml
AgeCommit message (Collapse)AuthorFilesLines
2018-04-16Change version of sdc-tosca dependencyArthur Martella1-16/+1
Rolling back version of sdc-tosca library to 1.3.0 to match sdc-distribution-client Removing the exclusion of jtosca and letting sdc-tosca pick the version it wants Change-Id: I5ac8775cce41a92c1964c7a2f24bf0a6b1e3e5df Issue-ID: SO-564 Signed-off-by: Arthur Martella <amartell@research.att.com>
2018-03-27sdc-tosca:1.3.3 depends on a SNAPSHOT artifactRob Daugherty1-0/+15
We have to exclude jtosca:1.3.4-SNAPSHOT and import jtosca:1.3.4. This is really a defect in SDC, but we have to work around it for M4. Change-Id: I4f204da9c5f3f601ae9a832203439bef7554079d Issue-ID: SO-536 Signed-off-by: Rob Daugherty <rd472p@att.com>
2018-03-27Dependency version updates for BeijingRob Daugherty1-33/+5
Update so/libs version to 1.2.1 Update aai-common version to 1.2.1 Update sdc-distribution-client version to 1.3.0 Update sdc-tosca version to 1.3.3 Change-Id: I6c8f1c5476efc4dc866bf765c265736ab70c12c7 Issue-ID: SO-536 Signed-off-by: Rob Daugherty <rd472p@att.com>
2018-03-23Remove forbidden dependencies to fix Jenkins jobArthur Martella1-1/+15
Change-Id: I5cdc138bb64d526d9b1baa8c2238cc9223004426 Issue-ID: SO-529 Signed-off-by: Arthur Martella <amartell@research.att.com>
2018-03-21added custom validators for use with openpojoBenjamin, Max (mb388a)1-6/+0
Change-Id: I7c9fdeb6bccddb1b7ec6bf845351731c3043aafa Issue-ID: SO-510 Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
2018-03-20NexusIQ security violation - httpclientRob Daugherty1-1/+0
Violation in: org.apache-httpcomponents : httpclient : 4.4.1, 4.3.1, 4.3.3, 4.5, 4.5.2 Fix: Upgrade httpclient to 4.5.5 and httpcore to 4.4.4 Change-Id: Ie31b853102eb2a4fc7fc16441a2a1c18a2b7fa35 Issue-ID: SO-507 Signed-off-by: Rob Daugherty <rd472p@att.com>
2018-03-19Fix the Jar vulnerability and licensingByung-Woo Jun1-1/+1
Updated Jar versions in pom.xml files Change-Id: I507b9348d7eabba879979a3cfeeefe9d850ecf4a Issue-ID: SO-457 Signed-off-by: byungwoojun<byung-woo.jun@ericsson.com>
2018-03-14AT&T 1712 and 1802 release codeRob Daugherty1-7/+7
This is code from AT&T's 1712 and 1802 releases. Change-Id: Ie1e85851e94bc66c4d9514a0226c221939531a04 Issue-ID: SO-425 Signed-off-by: Rob Daugherty <rd472p@att.com>
2018-03-09Remove redundant groupId inherited from parentMunir Ahmad1-1/+0
Change-Id: If1df4b792fca2a127e169e393268d63ef31d9ed1 Issue-ID: SO-437 Signed-off-by: Munir Ahmad <munir.ahmad@bell.ca>
2018-02-22Port SO artifacts to ONAP folder structureArthur Martella1-5/+5
Change-Id: Ib7aea4df7e6a31cf5e1e6513b89bed6f878537af Issue-ID: SO-372 Signed-off-by: Arthur Martella <amartell@research.att.com>
2017-12-01Bump minor versionJessica Wagantall1-1/+1
Bump minor version in preparation for Amsterdam branching. Change-Id: Ib72ca9cab2782a4fee15fff8f0653f0c53ad9f71 Issue-ID: CIMAN-120 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2017-11-16changed artifact versionseshukm1-1/+1
IssueId: SO-346 Change-Id: I4bd910032baa26c2aa154d3860bf4d34ecf7d9dd Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-11-02SO docker build issue fix in asdcseshukm1-1/+1
IssueId: SO-286 Change-Id: Ic9cb206c66401808487cf6fdbf1d08f36c6e8a7b Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-10-31second commit for the docker build issueseshukm1-2/+2
IssueId: SO-290 Change-Id: Ib097e14c7b06025a213e1cec1c2459fb59919c1a Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-10-06UT for the BPMN flowSeshu-Kumar-M1-149/+155
IssueId: SO-191 Change-Id: I167a7e96f4fd3a857a6c3e679dda132fc8a7f720 Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
2017-09-081710 Rebase - Second AttemptArthur Martella1-15/+42
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-04Another attempt to fix deploy problemRob Daugherty1-1/+1
The top level pom will contain: <groupId>org.openecomp.so</groupId> <artifactId>so</artifactId> Child modules will contain: <parent> <groupId>org.openecomp.so</groupId> <artifactId>so</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: I1976819df459d92937c6a4780959c32599dc3e71 Signed-off-by: Rob Daugherty <rd472p@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-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-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-02[MSO-8] Second step of the rebase for MSODeterme, Sebastien (sd378r)1-122/+122
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-3/+14
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-03-06Prepare for Release 1.0.0ChrisC1-1/+1
Change-Id: I54ab6edea94e61dd5dbfdb945bda2f51b5d8fc39 Signed-off-by: ChrisC <cc697w@intl.att.com>
2017-01-31Updating dependent artifact version in a few pom.xmlChrisC1-1/+1
Change-Id: I1b8d5e48da3ac4d1257214dab38706302d0acd10 Signed-off-by: ChrisC <cc697w@intl.att.com>
2017-01-31Initial OpenECOMP MSO commitChrisC1-0/+111
Change-Id: Ia6a7574859480717402cc2f22534d9973a78fa6d Signed-off-by: ChrisC <cc697w@intl.att.com>