Maven Dependency Conflict; MoreTypes.asTypeElement() method signature changed about elemento HOT 5 CLOSED

Ups! hehe we (both projects) really need to shade this dependency (as auto-common suggest) hehe 👍 we'll fix it in the next release in both projects.

from elemento.

It's already shaded in Elemento. I'll leave this open as a reminder and will close it once intendia-oss/autorest#5 has been fixed.

from elemento.

Uhm, but you applied the shade plugin 4month ago, then... what is this conflict? should be something wrong. Maybe the final pom still includes the dependency? shaded dependencies should be removed from the pom. Not sure... but something is wrong or the conflict will not appear.

from elemento.

Ok, I think I have found the problem. You are applying the shade plugin but the plugin by default just copy all your dependencies into the jar to create an uber-jar which is NOT what you want. You have actually partially configured the exclusion (aka. the lib-not-to-be-shaded) but or it is obsolete or it has not been correctly configured to match the group:artifact coordinates of the not-to-be-shaded packages. And finally, which is the actual problem here, it needs to relocate the conflicting packages, in this case, auto-service and auto-common classes. If you do not do that you are just copying the class file in your jar so it ends up conflicting anyway.

AutorREST fix here intendia-oss/autorest@993d9f0.

from elemento.

Yes that's right, my bad. I'm going to re-configure the shade plugin for Elemento.

from elemento.