Age | Commit message (Collapse) | Author | Files | Lines |
|
Updated with the error log messages
Changed the code to do string compare for eventName
update workflowaction to only persist if not resume
Issue-ID: SO-2363
Signed-off-by: Benjamin, Max (mb388a) <mb388a@att.com>
Change-Id: I139f2427ae0f0253a15cc51003318686568cb514
|
|
Change-Id: I95381232eeefcd247a66a5cec370a8ce1c288e18
Issue-ID: SO-670
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
UT workflowmessage WMAdapterRest
Issue-ID: SO-369
Change-Id: Id6cc113cdb7ac8e0601ab643478376ea6aa93d6b
Signed-off-by: Sindhu A <arcot.sindhuri@huawei.com>
|
|
mso-adapters workflowmessage UT coverage
Issue-ID: SO-369
Change-Id: I3cc4ad89d40457eb69dba9c88bed7ebea38de9a6
Signed-off-by: Sindhu A <arcot.sindhuri@huawei.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>
|
|
Change-Id: Ib7aea4df7e6a31cf5e1e6513b89bed6f878537af
Issue-ID: SO-372
Signed-off-by: Arthur Martella <amartell@research.att.com>
|
|
* Split bulk conditionals
* Split health checks to separate methods
* Fix minor issues
Issue-ID: SO-353
Change-Id: Ib6298bc488a94aa4fbb253e3894532708547533d
Signed-off-by: kurczews <krzysztof.kurczewski@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>
|
|
IssueId: SO-346
Change-Id: I4bd910032baa26c2aa154d3860bf4d34ecf7d9dd
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
When the workflow message adapter comes up, it throws a
FileNotFoundException because cadi.properties is absent.
This file is related to AAF, which is not in scope for
the Amsterdam release.
Issue: SO-341
Change-Id: I27239e215a523f8535d49d1888acc72deb35b270
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Issue-id: SO-223
Change-Id: I5f4d3f9ef78b68c890a32d3f6afc2a86f2064a6b
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
IssueId: SO-165
Change-Id: I7c2520af9394ceb600a5a25fa9acfd095d872a1d
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
Issue-Id : SO-117
Change-Id: Icdc64605b475e20af7e871135af327f7d0e38792
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
IssueId: SO-120
Change-Id: I59982b12d5b538b3f9765410ac26cbdde1844957
Signed-off-by: Seshu-Kumar-M <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>
|