End User Monitoring (EUM)

cancel
Showing results for 
Search instead for 
Did you mean: 

Android appdynamics-runtime 1.5.x.x generate warning in 'Configuration 'compile' is obsolete'

New Member

Android appdynamics-runtime 1.5.x.x generate warning in 'Configuration 'compile' is obsolete'

this warning is shown when using appdynamics-runtime 1.5.x.x 

 

WARNING: Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html

 

Therefore, using a lower version than 1.5 generate this issues

https://community.appdynamics.com/t5/End-User-Monitoring-EUM/Task-with-name-transformClassesWithDexF...

 

However, the above warning mentions that something will be removed at the end of 2018. which is sound, not good. Please update the library from using 'compile' to 'implementation'

 

After checking the library with the following command

 

./gradlew :app:dependencyInsight --configuration compile --dependency com.appdynamics:appdynamics-runtime:4.5.2.1229

 

it generates this as a result

 

> Task :app:dependencyInsight 
com.appdynamics:appdynamics-runtime:4.5.2.1229
   variant "default"
\--- compile

 

 

Android appdynamics-runtime 1.5.x.x generate warning in 'Configuration 'compile' is obsolete'
3 REPLIES 3

Re: Android appdynamics-runtime 1.5.x.x generate warning in 'Configuration 'compile' is obsolete'

This is a gradle warning saying that all dependencies should be added with either as `implementation` or `api`. I belive `compile` configuration has been deprecated with Android Gradle Plugin 3.0 . 

We are having the same issue.

When can we expect seeing this resolved ? 👀

Re: Android appdynamics-runtime 1.5.x.x generate warning in 'Configuration 'compile' is obsolete'

Hello, 

 

Can I get any updates on this ? 

Highlighted
New Member

Re: Android appdynamics-runtime 1.5.x.x generate warning in 'Configuration 'compile' is obsolete'

It would be really helpful to understand if/when this will be fixed?

 

Or if there is a workaround we can do before an SDK update is published.