Age | Commit message (Collapse) | Author | Files | Lines |
|
Replace duplicated regex patterns with more verbose constant
Change-Id: I21b5a1f8f00b8a8d059ab3998536b205ece892ce
Issue-ID: SO-353
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>
|
|
Issue-id: SO-214
Change-Id: I3f417fee04ae1fe2c1d0b7361ec0272e1b098302
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
Replaced with diamond symbol
Removed useless assignment to variables
Issue-Id: SO-187
Change-Id: If6fac39f2f8832fe6f7a00ed8f0a221e8d8fb897
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
Adding new test cases for Catalog DB Adapter
Change-Id: I1e809e39a9e41a26e87d1f7690ee46f42bccc076
Issue-ID: SO-171
Signed-off-by: Arthur Martella <amartell@research.att.com>
|
|
|
|
|
|
|
|
Issue-Id:SO-118
Change-Id: I7c69443dc5c17690605c4d1844823fd4307e9ccb
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
Issue-Id:SO-118
Change-Id: I61310f341d86b765d0eff82ff758fcc4922b6576
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
Issue-Id:SO-118
Change-Id: I744c8e8278157aefd001ebc27e35e77e115d3b71
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
SO-158
Change-Id: I82c0cfc4bc642fea34480feee0d5fb0bcebffe60
Signed-off-by: Ankit-Huawei <ankit.kumar.sinha1@huawei.com>
|
|
Replace the synchronized class "StringBuffer" by an unsynchronized one such as "StringBuilder"
Issue-Id:SO-118
Change-Id: Ica8ce815a834fcb8195e16096972b6f1627d7214
Signed-off-by: rama-huawei <rama.subba.reddy.s@huawei.com>
|
|
There were several issues. The wrong jackson provider was being selected,
which caused the exception, so we fixed that. Then we discovered that a
a URN mapping was missing, so we added that. Then we found that the
healthcheck wouldn't work because it's trying to check the default
process engine, which does not exist. We commented out that part of
the healthcheck to be able to resolve this high priority issue. A
new low priority issue will need to be created to follow up.
Change-Id: I327612a147333eeecd44915942cecd13959c4717
Issue-id: SO-139
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Issue-Id : SO-141
Change-Id: I0e901537013634dfc3f0950921c2ebbc2afa411f
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>
|
|
Change-Id: I3274dc7a64637cd7cf18d705258c0fc4985171ee
Signed-off-by: Gary Wu <gary.i.wu@huawei.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>
|