aboutsummaryrefslogtreecommitdiffstats
path: root/adapters
AgeCommit message (Collapse)AuthorFilesLines
2017-09-04Add VF-C Adapterc0014910731-0/+2698
Add VF-C Adapter to support VF-C APIs Change-Id: I4eb27755c8c5420343f457e0f9be37aa438361eb Issue-ID:SO-41 Signed-off-by: c00149107 <chenchuanyu@huawei.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 Daugherty12-53/+53
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 Daugherty12-54/+54
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 Daugherty12-57/+57
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)8-217/+388
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-03[MSO-8] Remove files that crash the commonBPMNDeterme, Sebastien (sd378r)12-1853/+0
Some files in commonBPMN have been removed as they prevent the war to be successfully deployed on Jboss + Remove rest interfaces files for catalog that should not be there anymore Change-Id: Iaf83f8b60610624e160feac8a96b7eaed7f161d1 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-05-02[MSO-8] Second step of the rebase for MSODeterme, Sebastien (sd378r)58-1264/+2903
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-05-02Merge "Fix resources leaks: CatalogDatabase"Christophe Closset1-22/+22
2017-04-11Fix resources leaks: CatalogDatabaseGary Wu1-22/+22
Change-Id: I3274dc7a64637cd7cf18d705258c0fc4985171ee Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2017-04-11Simplify MsoHeatEnvironmentParameter methodsGary Wu1-12/+3
Change-Id: I199008128f28903ea28ecfba437511c4c4a6c8e7 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2017-04-11[MSO-8] Update the maven dependencyxg353y138-1640/+9787
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-04-10Remove unnecessary use of Calendar.getInstance()Gary Wu3-13/+7
Calendar.getInstance() is expensive and unnecessary when we only need the system time. This change replaces the uses of Calendar.getInstance() with System.currentTimeMillis(). Change-Id: I476f8850f5eb88d20cf7249cca5bb2e9b671b45a Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2017-03-13Update to version 1.1.0ChrisC10-33/+33
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-31Updating dependent artifact version in a few pom.xmlChrisC1-4/+4
Change-Id: I1b8d5e48da3ac4d1257214dab38706302d0acd10 Signed-off-by: ChrisC <cc697w@intl.att.com>
2017-01-31Initial OpenECOMP MSO commitChrisC438-0/+53155
Change-Id: Ia6a7574859480717402cc2f22534d9973a78fa6d Signed-off-by: ChrisC <cc697w@intl.att.com>