Hi DCAE team,

All of a sudden, I am getting this error when building 
dcaegen2/platform/cdapbroker. This is supposed to be a warning but in this case 
it's turned into an error.
The reason seems to be that an old version of rebar executable (rebar 2.5.1) is 
pulled into dcaegen2/platform/cdapbroker/_build/default/lib/meck.
And also, in file 
dcaegen2/platform/cdapbroker/_build/default/lib/meck/rebar.config the compile 
flag "warnings_as_errors" is set.
I can remove this flag "warnings_as_errors" but I'd rather not touch this file 
because the whole "_build" subtree is pulled in at build time.

Any idea how to resolve this?

I have rebar3 & OTP 21 installed: rebar 3.5.0 on Erlang/OTP 21 Erts 10.0

Thanks,
Arash

________________________________
===> Compiling cowboy
_build/default/lib/cowboy/src/cowboy_handler.erl:97: Warning: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace
_build/default/lib/cowboy/src/cowboy_handler.erl:128: Warning: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace
_build/default/lib/cowboy/src/cowboy_handler.erl:255: Warning: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace
_build/default/lib/cowboy/src/cowboy_handler.erl:296: Warning: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace

_build/default/lib/cowboy/src/cowboy_rest.erl:81: Warning: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace
_build/default/lib/cowboy/src/cowboy_rest.erl:1010: Warning: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace

_build/default/lib/cowboy/src/cowboy_websocket.erl:174: Warning: call to 
crypto:sha/1 will fail, since it was removed in 20.0; use crypto:hash/2

===> Compiling leptus
_build/default/lib/leptus/src/leptus_handler.erl:560: Warning: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace

_build/default/lib/leptus/src/leptus_utils.erl:147: Warning: variable 'Rest' is 
unused

_build/default/lib/leptus/src/leptus.erl:289: Warning: erlang:now/0: Deprecated 
BIF. See the "Time and Time Correction in Erlang" chapter of the ERTS User's 
Guide for more information.

===> Compiling meck
===> Compiling _build/default/lib/meck/src/meck_code_gen.erl failed
_build/default/lib/meck/src/meck_code_gen.erl:198: erlang:get_stacktrace/0: 
deprecated; use the new try/catch syntax for retrieving the stack backtrace

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 51.604 s
[INFO] Finished at: 2018-07-13T15:38:19-04:00
[INFO] Final Memory: 25M/290M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
(compile script) on project cdapbroker: Command execution failed.: Process 
exited with an error: 1 (Exit value: 1) -> [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]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
________________________________

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>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11125): https://lists.onap.org/g/onap-discuss/message/11125
Mute This Topic: https://lists.onap.org/mt/23395864/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to