Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
Combine designand run time paramters.
Change-Id: Ide61cb14697f137e73308b29b721cedb1bd3e13e
Issue-ID: SO-453
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
|
|
Change-Id: Ib7aea4df7e6a31cf5e1e6513b89bed6f878537af
Issue-ID: SO-372
Signed-off-by: Arthur Martella <amartell@research.att.com>
|
|
Added unittests for ResponseExecptionMapperImpl and refactored one test for CompleteMsoProcessTest
Issue-ID: SO-374
Signed-off-by: biniek <lukasz.biniek@nokia.com>
Change-Id: I359daf14d2a913829721fff3f2d340c6e893aa13
Signed-off-by: biniek <lukasz.biniek@nokia.com>
|
|
Bump minor version in preparation for Amsterdam
branching.
Change-Id: Ib72ca9cab2782a4fee15fff8f0653f0c53ad9f71
Issue-ID: CIMAN-120
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
|
|
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>
|
|
IssueId: SO-346
Change-Id: I4bd910032baa26c2aa154d3860bf4d34ecf7d9dd
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
IssueId: SO-346
Change-Id: Ib18e075a6074b59170cdb26f60260dd5882886d8
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
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>
|
|
Several failed attempts to split the BPMN application into
multiple applications with separate camunda process engines
have left a mess of confusing classes and process engine
definitions.
In the Amsterdam release, there should be only one BPMN
application war. This is MSOInfrastructureBPMN.
MSOCommonBPMN should not be deployed as a separate
application. Its classes are compiled into a jar and
this is included inside MSOInfrastructureBPMN.
The MSOInfrastructureBPMN application should use the
"default" process engine.
WorkflowAsyncInfrastructureResource and
MSOCommonApplication classes are not needed.
Issue: SO-322
Change-Id: Ifdb3b33541346b561a16361d1aa791e8342a34fa
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Issue-Id: SO-309
Change-Id: I998d5573d60d99987bb99133967ca012ef8dba6f
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
modified RestClient to accept rest properties
Issue-Id: SO-309
Change-Id: I68bd88f9f942573dc470dda2eb60dc747e782768
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
moved SDNO beans to their own package
Issue-Id: SO-309
Change-Id: I0b35edfe0ac3ad336320d8bc62d2efd98fff1b0b
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
added enum for ServiceType in policy
Issue-Id: SO-309
Change-Id: Icdc95b237a427bbacac4cf5d815fc71cebb91675
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
dmaap rest client implementation
Issue-Id: SO-309
Change-Id: I1bf8b85820524adca462d7d96c4c0beef5892864
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
dmaap client interface for SO component
Issue-Id: SO-309
Change-Id: Ieccfb22678c52af7ffcf8750a38462ba32486182
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
added required guava dependency to pom.xml
Issue-Id: SO-309
Change-Id: I3096bf54888e4960e60bb73b13d8cd3223217271
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
IssueId: SO-286
Change-Id: Ifecb18013568608edb4d931d23d4df8ae629102e
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
Issue: SO-159
Change-Id: Ic3e442eaa7603b52a2e32e8395ca8ff9bc069f75
Signed-off-by: Krzysztof Kwiecien <krzysztof.kwiecien1@orange.com>
|
|
Issue-Id : SO-117
Change-Id: Icdc64605b475e20af7e871135af327f7d0e38792
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|