Re: DCAE Build Error: dcaegen2/platform/cdapbroker ?


Vijay Venkatesh Kumar
 

The process will be to mark the repository as ready only and disable all Jenkins jobs (repo deletion may not be an option).

 

We are looking to onboard other analytics platform into DCAE (e.g PNDA and Flink, both having some community interest) in coming releases. Depending on how those integration comes along, CDAP can be deprecated.

 

Regards,

Vijay.

 

From: CARPENTER, TOMMY J
Sent: Monday, July 16, 2018 7:19 PM
To: HEKMAT, ARASH <arash.hekmat@...>
Cc: VENKATESH KUMAR, VIJAY <vv770d@...>; onap-discuss@...
Subject: Re: DCAE Build Error: dcaegen2/platform/cdapbroker ?

 

I had thought there was a formal process to deprecate something, rather than just deleting a repo, and perhaps that this had to be approved by the TSC. There are two other code sources in DCAE relating to this; the CDAP plugin, as well as the CDAP deployment blueprints. Formally removing CDAP would mean deleting all such code. 


On Jul 16, 2018, at 7:12 PM, HEKMAT, ARASH <arash.hekmat@...> wrote:

Thanks Vijay, Tommy,

 

I found the cause of the build error though. I had installed “Erlang/OTP 21” which has deprecated some APIs. Once I downgraded to “Erlang/OTP 20” the build succeeded.

 

In any case, if the CDAP Broker is deprecated it would be best to delete the repo dcaegen2/platform/cdapbroker from ONAP Gerrit.

 

Thanks,

Arash

 

From: CARPENTER, TOMMY J (TOMMY J) <tommy@...>
Sent: Friday, July 13, 2018 5:41 PM
To: VENKATESH KUMAR, VIJAY <vv770d@...>
Cc: onap-discuss@...; Arash Hekmat <Arash.Hekmat@...>
Subject: Re: DCAE Build Error: dcaegen2/platform/cdapbroker ?

 

Yes the CDAP Broker is not a released or built artifact in R2+. I don’t know what the formal deprecation process is, but consider it deprecated since R1. Probably many things in it are out of date including its compatibility with CDAP. 


On Jul 13, 2018, at 5:35 PM, VENKATESH KUMAR, VIJAY <vv770d@...> wrote:

Hi Arash,

   Just FYI, the R2 deployment of DCAE does not include CDAP and hence CDAP broker was not deployed either (this may be deprecated in later releases).

 

CDAP Broker code is largely un-modified since R1; looking through the build report – seems normal and latest build was successful.

 

Suspect if local setup issue; looping Tommy who could give some pointers.

 

Regards,

Vijay

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of HEKMAT, ARASH
Sent: Friday, July 13, 2018 4:29 PM
To: onap-discuss@...
Subject: [onap-discuss] DCAE Build Error: dcaegen2/platform/cdapbroker ?

 

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,

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,

Join onap-discuss@lists.onap.org to automatically receive all group messages.