Age | Commit message (Collapse) | Author | Files | Lines |
|
This artifact is not actually used by SO.
Removed it from the poms.
Change-Id: Icfeb3026581996bc980a223232a305c488a01fb2
Issue-ID: SO-1065
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Upgrade to fasterxml.jackson 2.8.10. This is the latest version
that seems to work with our code on springboot 1.5.13.RELEASE.
Change-Id: I734f84c18e53218f111fb08c959a67ee0a2e6014
Issue-ID: SO-856
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Seperate out Beans and repositories for RequestDB
Change-Id: I67d6597d580e9828b6bb8faafaea7e09cc6467c0
Issue-ID: SO-999
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Fix Autoincrement of ID field in table
Fix accidental removal of method
Update usage of requestdb client
removed unused imports in common tasks and test
Fix broken branch, have unit tests pass
references
the Epic branch
Fix broken branch from compiling
committing classpath for vfc adapter cause its not going away
added in the fail case for when there are no profiles
removed second set of adapters in application test yml
removed double adapters in request db application test
added jpa repo dependency to the so bpmn folder pom
add creation timestamp column to the table
added in null checks for Config returned from policy
switched to string in requestprocess with jenerate
switched to string in requestprocess with jenerate
updated aai version in common pom to 605 from 591
renamed the db scripts for flyway sync to register
added endpoint to application test yml for failing test
...
Change-Id: I800f837ea75d7cdff740dc3a387e4d7654cfd085
Issue-ID: SO-972
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
cxf 3.2.5 also requires us to move to javax.ws.rs-api 2.1
javax.ws.rs-api 2.1 is fully backwards compatible with 2.0
it will not be a problem with our other dependencies
Issue-ID: SO-850
Change-Id: I2a6d9c5d6fb9025de8e5b4a00788275d7cc496a1
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Issue-ID: SO-799
Change-Id: Ia403872b2d81e7277f9329d6be08df6e04f7bd27
Change-Id: Ia403872b2d81e7277f9329d6be08df6e04f7bd27
Signed-off-by: Smokowski, Steve (ss835w) <ss835w@us.att.com>
|
|
Change-Id: I95381232eeefcd247a66a5cec370a8ce1c288e18
Issue-ID: SO-670
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Changed versions from 1.3.0-SNAPSHOT to 1.3.0 for appc maven artifacts:
client-lib
client-kit
Change-Id: Ie4d98b400c7557655c74c3225b089c2ccc54b0cb
Issue-ID: SO-682
Signed-off-by: Michal Kabaj <michal.kabaj@nokia.com>
|
|
To prevent appc snapshot problem
Also change appc version to SNAPSHOT
Change-Id: Ifce05b7f44ccc70a2d654526d67da873dd325dcd
Issue-ID: SO-605
Signed-off-by: Arthur Martella <am153x@att.com>
|
|
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>
|
|
Change commons-httpclient : commons-httpclient to org.apache.httpcomponents : httpclient : 4.5.5
Change-Id: I9ba93af3fc66ca31bc70d4a96a9ca977c9747aa6
Issue-ID: SO-537
Signed-off-by: Arthur Martella <amartell@research.att.com>
|
|
We should use 1.3.0, not 1.3.0-SNAPSHOT
Change-Id: I6568da027d7a15e580f62961a0bc6bf3fcd68359
Issue-ID: SO-536
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
|
|
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>
|
|
Upgraded Jar depdendencies in pom.xml
Change-Id: I0bc67d18a9b99f70676659c4ac78975dcf4d6972
Issue-ID: SO-537
Signed-off-by: byungwoojun<byung-woo.jun@ericsson.com>
|
|
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>
|
|
Change-Id: I5cdc138bb64d526d9b1baa8c2238cc9223004426
Issue-ID: SO-529
Signed-off-by: Arthur Martella <amartell@research.att.com>
|
|
Updated Jar versions in pom.xml files
Change-Id: I507b9348d7eabba879979a3cfeeefe9d850ecf4a
Issue-ID: SO-457
Signed-off-by: byungwoojun<byung-woo.jun@ericsson.com>
|
|
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>
|