aboutsummaryrefslogtreecommitdiffstats
path: root/bpmn/MSOMockServer/pom.xml
AgeCommit message (Collapse)AuthorFilesLines
2017-11-09Move unit test mocks to test scoped jarRob Daugherty1-100/+0
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>
2017-10-19Restore MSOMockServer to the buildRob Daugherty1-0/+100
Classes in this artifact are needed for unit tests. For a long term solution, we should find a way to build these classes into a test-scoped artifact. Issue: SO-242 Change-Id: I1a57fead07250c841a9f59afb805aea26c7bc102 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-10-10Delete unwated codeseshukm1-100/+0
Change-Id: I05931195c51f171a59bb8f831e8fbbf7fd7ea11f IssueId: SO-202 Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-09-12Fix for SONAR critical issuesseshukm1-0/+5
Issue-Id : SO-117 Change-Id: Icdc64605b475e20af7e871135af327f7d0e38792 Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
2017-08-04Failed to deploy so artifacts in nexus (again)Rob Daugherty1-2/+2
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 Daugherty1-2/+2
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 Daugherty1-2/+2
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-04-11[MSO-8] Update the maven dependencyxg353y1-0/+95
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>