Please clean .m2 and add to mvn command -U
From: Chenchuanyu [mailto:chenchua...@huawei.com]
Sent: Tuesday, September 19, 2017 9:30 AM
To: Elhay Efrat <elhay.efr...@amdocs.com>; onap-discuss@lists.onap.org
Subject: 答复: [SO]SO Maven Build Issue
The command I use is ‘mvn install �CDmaven.test.skip=true’. And I have the
full internet access, it is windows env.
It looks like there is some problem with the below dependency configuration.
client-kit-1.1.0.pom cannot be found at nexus repo. But I’m not sure why it
build success in jenkins.
[cid:image001.png@01D3313A.C5FDDFD0]
发件人: Elhay Efrat [mailto:elhay.efr...@amdocs.com]
发送时间: 2017年9月19日 12:00
收件人: Chenchuanyu;
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
主题: RE: [SO]SO Maven Build Issue
Yes , please send me the mvn command that you are doing ... And second you have
full internet access ? Is it Linux or windows ?
________________________________
From: Chenchuanyu
Sent: Tuesday, September 19, 2017 2:20:49 AM
To: Elhay Efrat; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: 答复: [SO]SO Maven Build Issue
Hi Elhay,
Thanks for your reply, I think the jar exists in nexus, the project build
successful in Jenkins. But failed in my local env. Is there any other
suggestion for this?
Jenkins build log:
[INFO] MSOMockServer ...................................... SUCCESS [ 1.790 s]
[INFO] MSO REST Client API ................................ SUCCESS [ 0.211 s]
[INFO] MSOCommonBPMN ...................................... SUCCESS [01:36 min]
[INFO] MSOInfrastructureBPMN .............................. SUCCESS [03:50 min]
[INFO] MSO URN Mapping Cockpit Plugin ..................... SUCCESS [ 0.284 s]
[INFO] MSOCockpit ......................................... SUCCESS [ 10.610 s]
[INFO] MSO Packages ....................................... SUCCESS [ 0.004 s]
[INFO] MsoDeliveries ...................................... SUCCESS [ 14.837 s]
[INFO] MSO Docker Deliveries .............................. SUCCESS [21:44 min]
[INFO] Arquillian Unit Testing on MSO ..................... SUCCESS [01:47 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 32:01 min
[INFO] Finished at: 2017-09-18T03:47:44+00:00
[INFO] Final Memory: 191M/798M
[INFO] ------------------------------------------------------------------------
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 2189 killed;
Thanks,
Chuanyu Chen.
发件人: Elhay Efrat [mailto:elhay.efr...@amdocs.com]
发送时间: 2017年9月18日 11:54
收件人: Chenchuanyu;
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
主题: RE: [SO]SO Maven Build Issue
This jar is exist in nexus2 ?( With this version ? )
org.openecomp.appc.client:client-kit:jar:1.1.0
-- Sent from my Android Device
________________________________
From:
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>
on behalf of Chenchuanyu
Sent: Monday, September 18, 2017 1:37:34 AM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] [SO]SO Maven Build Issue
Hi, SO team,
After 1710 merge, I build SO project failed , does anyone know how to fix
that?
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] so ................................................. SUCCESS [ 1.139 s]
[INFO] MSO Common classes ................................. SUCCESS [ 6.656 s]
[INFO] API Handler ........................................ SUCCESS [ 0.040 s]
[INFO] mso-requests-db .................................... SUCCESS [ 5.966 s]
[INFO] mso-catalog-db ..................................... SUCCESS [ 9.975 s]
[INFO] ECOMP MSO API Handler common ....................... SUCCESS [ 1.557 s]
[INFO] MSO Status Control module .......................... SUCCESS [ 0.671 s]
[INFO] mso-api-handler-infra .............................. SUCCESS [ 14.955 s]
[INFO] MSO Adapters ....................................... SUCCESS [ 0.038 s]
[INFO] mso-adapter-utils .................................. SUCCESS [ 5.703 s]
[INFO] mso-adapters-rest-interface ........................ SUCCESS [ 2.724 s]
[INFO] mso-network-adapter-async-client ................... SUCCESS [ 6.213 s]
[INFO] mso-network-adapter ................................ SUCCESS [ 27.277 s]
[INFO] mso-sdnc-adapter ................................... SUCCESS [ 5.310 s]
[INFO] mso-tenant-adapter ................................. SUCCESS [ 5.566 s]
[INFO] mso-vnf-adapter-async-client ....................... SUCCESS [ 2.807 s]
[INFO] mso-vnf-adapter .................................... SUCCESS [ 12.534 s]
[INFO] mso-requests-db-adapter ............................ SUCCESS [ 4.880 s]
[INFO] mso-catalog-db-adapter ............................. SUCCESS [ 2.712 s]
[INFO] mso-workflow-message-adapter ....................... SUCCESS [ 3.408 s]
[INFO] mso-vfc-adapter .................................... SUCCESS [ 3.080 s]
[INFO] asdc-controller .................................... SUCCESS [ 12.856 s]
[INFO] BPMN Subsystem ..................................... SUCCESS [ 0.040 s]
[INFO] MSOCoreBPMN ........................................ SUCCESS [ 7.397 s]
[INFO] MSOMockServer ...................................... SUCCESS [ 5.023 s]
[INFO] MSO REST Client API ................................ SUCCESS [ 0.599 s]
[INFO] MSOCommonBPMN ...................................... FAILURE [ 0.907 s]
[INFO] MSOInfrastructureBPMN .............................. SKIPPED
[INFO] MSO URN Mapping Cockpit Plugin ..................... SKIPPED
[INFO] MSOCockpit ......................................... SKIPPED
[INFO] MSO Packages ....................................... SKIPPED
[INFO] MsoDeliveries ...................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:33 min
[INFO] Finished at: 2017-09-15T17:26:25+08:00
[INFO] Final Memory: 81M/446M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project MSOCommonBPMN: Could not resolve
dependencies for project org.openecomp.so:MSOCommonBPMN:war:1.1.0-SNAPSHOT: The
following artifacts could not be resolved:
org.openecomp.appc.client:client-kit:jar:1.1.0,
org.openecomp.appc.client:client-lib:jar:1.1.0: Failure to find
org.openecomp.appc.client:client-kit:jar:1.1.0 in
https://nexus.onap.org/content/repositories/eclipse was cached in the local
repository, resolution will not be reattempted until the update interval of
onap-eclipse has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
Thanks,
Chuanyu Chen.
***************************************************************************************
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
**************************************************************************************
***************************************************************************************
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by
persons other than the intended recipient(s) is prohibited. If you receive
this e-mail in error, please notify the sender by phone or email immediately
and delete it!
***************************************************************************************
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
<https://www.amdocs.com/about/email-disclaimer>
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
